>Mike,
>
>I got a little bit further, but now I receive client access invalid token error. Here is my code:
>
>SQLEXEC(lnHandle, "UPDATE QS36F.GMBIAP6 SET GMBIAP6.WSBTC = 'Y';
> WHERE GMBIAP6.WDC=' ' & GMBIAP6.WSBTC = ' '")
>
>It seems to not like the . between QS36F & GMBIAP6. Any suggestions? Thanks! :)


What is the & for? I don't see that in the standard SQL syntax. Do you mean:

SQLEXEC(lnHandle, "UPDATE QS36F.GMBIAP6 SET GMBIAP6.WSBTC = 'Y' ;
WHERE GMBIAP6.WDC=' ' AND GMBIAP6.WSBTC = ' '")

Or do you mean:

SQLEXEC(lnHandle, "UPDATE QS36F.GMBIAP6 SET GMBIAP6.WSBTC = 'Y' ;
WHERE GMBIAP6.WDC=' ' OR GMBIAP6.WSBTC = ' '")

The AS400 supports only standard SQL implementation. You should get your hands on an AS400/DB2 SQL Reference book. There are a lot of things you can do with VFP and SQL server's SQL that are not supported on the AS400. It can get on your nerves a bit after being spoiled on VFP! Remember how we used to have to do a left outer join.

BTW - what software are you connecting to your AS400 with? If you are not using IBM's latest release of Client/Access (lightning) with ADO support you will be impressed. Data throughput if fast, about 8 times faster than the previous release! During testing we moved 40Meg in the 1 minute range (Bottlenecked the 10 Mbit network segment). There is a memory leak to deal with (IBM's working the issue) but this is generally not a problem unless moving large recordsets. You can do a workaround by using out-of-process COM to handle the data. Memory is released when the COM terminates.

Regards,
Mike