Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Error 1812 - SQL: Statement too long
Message
De
22/11/2004 08:24:11
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
 
 
À
22/11/2004 05:23:23
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:
00963451
Vues:
10
>Yes with CA and VFP8+. However possible with earlier too. Then where slightly differs:
>
>where oldval(myview.myTimeStamp) == curval(myView.myTimeStamp)
>
>Actually rethinking this where would be easier to construct this way for both the CA and w/o CA (just add both PK and timestamp as keyfields and mark at least timestamp as updatable).
>Cetin

In this case, where would you update the timestamp? Is it possible to do this in the table definition? (I think there will be some problems here.) Or does it have to be done at the form level?

===

In any case, it might be worthwhile to switch to VFP version 8 or 9, eventually. I am still using version 6 for now, but perhaps I can convince my client to switch.
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