Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DiffGram Size Limit - BUG?
Message
From
12/10/2004 14:39:50
 
 
To
06/10/2004 17:56:42
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00949243
Message ID:
00950788
Views:
8
Since the CompareMemo = .T. was the problem in this case, it seems that the real problem is the length limitation of the CursorAdapter's auto-generated WHERE clause. This would be a function of the number of updatable fields as well as the length of the field names.

Is this correct? If so, are there any plans to remove limits on CA auto-generated commands?

>>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.
>>
>
>Are you using 'NATIVE' data source type for the CursorAdapter? The CompareMemo=.T. can be a problem, if all memo fields are added into the WHERE clause, the auto-generated command might exceed the limit. What WhereType are you using? You can check the length of auto-generated command in BeforeUpdate/BeforeDelete event and confirm if this is the case.
>
>
>>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?
>>
>
>I am pretty sure this error is not related to the DiffGram size nor it is related to the linefeeds. The linefeeds inserted because XMLAdapter.FormattedOutput property is .T. by default.
>
>Thanks,
>Aleksey.
- Jeff
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform