I don't have experience with a Sybase database; however, I experienced a weird problem with a VFP 3.0 database that had stored procedures. The stored procedures were compiled in 3.0 which made the database UNREADABLE\UNUSABLE to my 5.0 application. Maybe your database's stored procedures were compiled under a different version from what you are using. Until Microsoft fixes the compiled stored procedures problem (i.e., by creating a different memo field each version - or at least for the version being run) I will keep my stored procedures in a .prg file (as in the old days) and issue a SET PROCEDURE TO Xfilename ADDITIVE.