Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQLEXEC()
Message
De
14/12/1998 09:38:28
 
 
À
14/12/1998 09:22:47
Andy Roth
Neyenesch Printers
Californie, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Titre:
Divers
Thread ID:
00167141
Message ID:
00167149
Vues:
21
>Is there a limit to the character string that can be used in SQLEXEC()?
>
>I had a query give me an error message if I used the tables names but if I didn't the query worked
>
>
>Example of working:
>
>SQLEXEC(,gnconnect,"SELECT ljob, closedate, cogsdate,;
> invno, indate;
> FROM bbjthead, arjob, arjobhd;
> WHERE bbjthead.ljob=arjob.ljob
> AND closedate in null;
> AND cancldate is null;
> AND arjob.invno=arjobhd.invno;
> ORDER by ljob",;
> "wips")
>
>Example of nonworking:
>
>SQLEXEC(,gnconnect,"SELECT bbjthead.ljob, bbjthead.closedate, bbjthead.cogsdate,;
> invno, indate;
> FROM bbjthead, arjob, arjobhd;
> WHERE bbjthead.ljob=arjob.ljob

If this isn't a typo, there is a missing ; here.

> AND bbjthead.closedate in null;
> AND bbjthead.cancldate is null;
> AND arjob.invno=arjobhd.invno;
> ORDER by ljob",;
> "wips")
>
>It errored out on the "wips") line.
>unrecognized comman/phrase
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform