Stored Procedures in VFP 8

[ToddWW]

I've been using stored procedures in VFP 7 using the following steps.

OPEN DATABASE fbdata1 SHARED
MODIFY PROCEDURE

With VFP 7, I could write procedures, etc... and call them from my ASP web pages. Everything would work great. After making any changes, I could just hit File / Save and the procedure would save and I could test it immediately.

Since I upgraded to VFP8 (Including OleDb8), it doesn't seem to work that way any more. If I add or modify my procedures and hit File / Save, it doesn't stick. Sometimes I have to re-open then quit VFP and that will work. Other times I have to reset IIS on the web server. Very strange but I was wondering if I'm missing something.

My goal is to continue to be able to add / modify procedures in VFP's stored procedure without opening the database exclusively or having to reset web services, etc.. Anyone else run into this ?

ToddWW

 

[Mike Lewis]

Todd,

Are you saying that you can't run your SPs from ASP? If so, can you run them from within VFP?

If it is ASP where the problem occurs, you have to make sure you have the latest OLE DB provider for VFP (not the ODBC driver). There were severl new DBC-related features in VFP 8.0 that the earlier driver doesn't support.

You can determine if that's the problem by trying to call the procedures from within VFP. Alternatively, try working with a DBC that you created in an earlier version, and which hasn't been modified in 8.0.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[Olaf Doschke]

What you modify there is source code. "compile before saving" is an option you can set for PRG files, I doubt this makes a difference, but in fact you only get new object code by COMPILE DATABASE. And that needs exclusive access.

Bye, Olaf.