Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Error 1812 - SQL: Statement too long
Message
De
22/11/2004 05:23:23
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
À
21/11/2004 18:39:25
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
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:
00963424
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

>Ah, with CursorAdapters. I think that is VFP8 or later, right? I see that it gives you possibilities that are not otherwise available.
>
>Thanks a lot for your comments.
>
>>No not in trigger just modify your where clause (with CA you've control over updatecmd):
>>
>>where pkkey = pkkey and myTimestamp = curval(myView.myTimeStamp)-1
>>
>>* myTimeStamp is incremented by one in CA cursor
>>Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform