Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL: Statement too long (error 1812) - no apparent reason?
Message
De
24/07/1999 02:29:45
Al Doman (En ligne)
M3 Enterprises Inc.
North Vancouver, Colombie Britannique, Canada
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
SQL: Statement too long (error 1812) - no apparent reason?
Divers
Thread ID:
00245681
Message ID:
00245681
Vues:
51
I'm using VFP5.0a (build 415). I've got a view-based form that creates a parameter object using SCATTER...NAME and passes it to another (modal) form (which uses a private datasession).

On returning from the modal form, I'd ideally like to issue GATHER...NAME to update the view form's fields with updated values from the parameter object. However, if I try, I get the above error.

If I try to REPLACE just a few view fields from the parameter object, it works. If I try a REPLACE of all, or slightly more than half, same error.

When the modal form is closed, the .Activate of the view form is eventually called, which refreshes the view form. The error handler is reporting the problem in a piece of code that works perfectly in every other circumstance and which contains no SELECT - SQL statements even approaching the limit.

The view-based form is fairly complex. Has VFP been known to throw bad/misleading error messages when the going gets tough?

Any help or wild-assed guesses greatly appreciated.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform