Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Error 1812 - SQL: Statement too long
Message
De
20/11/2004 19:33:00
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
À
20/11/2004 19:26:47
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Versions des environnements
Visual FoxPro:
VFP 8
OS:
Windows XP
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
00963256
Message ID:
00963259
Vues:
10
>Roy,
>Check sys(3055). Also if it's not a must for you to check with modified fields change wheretype to KeyFieldsOnly (would be a simple fix).
>Cetin

Just a few days ago, I was participating in another thread, about the same issue.

If I understand correctly, changing the WhereType to KeyFieldsOnly would make you lose the automatic update management. IOW, VFP would not detect if another user has made changes. Do you understand it this way, too? What would be the solution?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform