>I am not convinced. The property is perfectly capable of holding a valuea of that size, I am just not able to pass it without first assigning it to a variable.
>Secondly, property values are not stored internally in character fields, but in memo fields.
>
>Rick?

Well, at least the initial values are. I assume run-time values are just in memory. The initial value of custom properties are stored in the memo field named "Properties" in an SCX or VCX table. But each custom property doesn't have it's own memo field, rather the values are all stored in a single memo field whose contents look like this:
DoCreate = .T.
myprop = abcdefghijklmnopqrstuvwxyz
Name = "FrmOK1"
cmdOK.Name = "cmdOK"

The longest string I've been able to stuff into a custom property using the property sheet in VFP 5.0a is 255 (sic) characters. If you hack the SCX and make the value of myProp longer than 255 characters, you get a "Error loading file... property value is out of bounds" error and the form won't run. So there is apparently an internal limit of 255 characters to the length of the intial value of a character-type property.

I don't know the internal mechanics of how a parameter is passed to another form , but apparently something happens when passing a property that doesn't happen when passing a memvar. BTW I found that the limit when passing a property is 254 characters (but not 255... why?). Maybe someone who knows the internals of VFP will weigh in here. It's certainly an interesting problem.