Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DiffGram Size Limit - BUG?
Message
From
06/10/2004 17:34:25
 
 
To
06/10/2004 15:20:51
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00949243
Message ID:
00949373
Views:
22
No,

The CA KeyFieldList is OK as well as all other CA properties. Also set the correct XMLField.KeyField property just in case.

Could there be a problem with CompareMemo = .T. with 50 memo fields? I know that is an extreme number of memo fields - using them for metadata.

Also checked the DiffGram. Where are all the linefeeds (over 1,000) coming from? Is this creating the problem? Why does the XMLAdapter create linefeeds?

>Hi Jeff,
>
>Take a look If the message #806254 is applicable in your scenario. If not, please post complete repro code.
>
>Thanks,
>Aleksey.
>
>>Got an error from a COM+ server that has been in use for over a year.
>>
>>The error occurs when using an XMLAdapter to apply a DiffGram to a CursorAdapter only when the DiffGram contains a lot of memo fields (20 in this case) each containing a relatively small amount of data. The error number is 18: "Line is too long - The maximum length for a command line (8,192 bytes) has been exceeded."
>>
>>To be specific, the following error was logged at line 357 where loXA.Tables(1).ApplyDiffgram("", loCA) is executed:
>>
>>
>>COM Error
>>Server : xmlsession
>>Error# : 18
>>Method : updatecursorxml()
>>Line#  : 357
>>Source : create cursor XMLTable_2A480336_BD66_4EFD_8D99_54A3C6B093D2_ from array _XMLFieldsArray_C32668E1_4C99_42FF_B8CE_DDE9B8DCE360_  (This is a VFP internal command that was trapped)
>>Cause  : Line is too long.
>>
>>
>>Upon further investigation the following condition existed just before the attempt to apply the DiffGram:
>>
>>LEN(tcXMLDiffGram) = 35671
>>LEN(loCA.cursorschema) = 1383
>>LEN(loCA.updatablefieldlist) = 1231
>>LEN(loCA.updatenamelist) = 3793
>>
>>One of the above seems to be exceeding some internal limit.
>>
>>Any one had this problem? I think this is a bug.
- Jeff
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform