experchange > solomon

walrus (07-28-09, 10:41 PM)
I created a new table with two fields:
Field1 nvarchar(10)
Field2 nvarchar(648)
And modified the PV property of my customized field.

I imported a PV line (Import posbile values option), but when I press F3 in
my customized field, Solomon displays the next message.

"Microsoft Visual C++ Runtime Library"
Buffer overrun detected!

Does exists a size limit for the PCV's fields?, Should I reduce then size of
my field2?

Regards.
Barry Flynn (07-28-09, 11:35 PM)
Walrus

Couple of thoughts.

1. Solomon itself does not use nvarchar fields in any tables (to my
knowledge).
I suggest sticking with "char(n)" fields, which are widely used.

2. All Solomon tables have
[tstamp] [timestamp] NOT NULL
as the physically last field in the table.

Note that the Class for the table does NOT incude the tstamp field - that
field is used by the kernel, and is never "seen" by the VBTools screen.

> Does exists a size limit for the PCV's fields?, Should I reduce then size
> of
> my field2?


Hmmm - not totally sure offhand.
There may be two different factors - any possible limit (imposed by either
SQL Server, DB Library, or the Solomon Kernel) on the size of a database
field, and any limit imposed by Solomon's Masked Text control.
And possibly a third area - any limit imposed by the kernel's PV
Processing...

Just for testing purposes, you may want to reduce it to, say, 100.
Then, when you get things working, try increasing it again & see what
happens...

As far as I recall, the largest char fields I have used in 7.x tend to be
100, but I don't think any have PV's.
In version 6.x, I have a table with a couple of 250 char fields, but neither
appears on any screen.

Hope that helps...

Barry
walrus (07-29-09, 04:33 PM)
Thanks again Barry, I'm going to run some test on it.

Regards

"Barry Flynn" wrote:
[..]
walrus (07-29-09, 05:21 PM)
Hi Barry you were right, I changed the type of field2 (nvarchar to char), and
added a tstamp field.

I tried different lengths for the field2, 100, 200, 255, 256, 300 and
finally 700 everything works perfectly.

Thanks Barry

"Barry Flynn" wrote:
[..]
rrosenhagen (03-25-10, 03:31 PM)
I would like to create one table to hold multiple values for multiple PV
lookup fields. For instance, a field that would store the colors available
for an inventory item, or source of an order taken, or what manager approved
a cancelled order. How would I put all these values into one PV lookup table
that could be used by all my custom PV fields?
Tony Murnion (03-25-10, 04:56 PM)
You could create one table to hold the data values. You would need a
column in the table to differentiate the colors from the source from the
manager approval. For example, you might call the column PVType and
populate it with "COLOR" for those data rows that relate to color of the
inventory item. In the PV for the color field, your select where clause
would include "pvtype = 'COLOR'". You would then only get the records
that relate to color.

Tony Murnion
AZ Technology Solutions, Inc.
Anderson ZurMuehlen & Co., P.C.
828 Great Northern Blvd
PO Box 1040
Helena, MT 59624
406.457.7008

-----Original Message-----
From: rrosenhagen
[mailto:rrosenhagen[remove_this]@rcsgifts[remove_this].com]
Posted At: Thursday, March 25, 2010 7:31 AM
Posted To: microsoft.public.solomon
Conversation: Does PV's fields size has a limit?
Subject: Re: Does PV's fields size has a limit?

I would like to create one table to hold multiple values for multiple PV
lookup fields. For instance, a field that would store the colors
available
for an inventory item, or source of an order taken, or what manager
approved
a cancelled order. How would I put all these values into one PV lookup
table
that could be used by all my custom PV fields?
Similar Threads