>I posted this question yesterday and I must have asked the wrong questions or worded them poorly. So I will try again.
>1) I would like to know when Stored procedures are fired. Can you remove the programming from FOXPRO and trigger the SP by file access or is there a connection between the VFP code and the DBC?

They are run when you call them. SPs are not like triggers (although your triggers could call SPs - see below), they have no set time time they are fired. They just exist ready to be called when you need them (e.g. from a trigger or Default value).

Triggers fire when you Insert, Update or Delete from a table. The trigger can be be confirgured to call an SP.

>2) Can anybody offer direction to the gotcha's involed in taking the tables out of a DBC and putting them in Remote views in SQL server?

If you upsize the DBC to SQL Server 7, you will need to convert the SPs and triggers to T-SQL code.

I can't really give you any feedback on remote views as I don't use them. I handle that type of stuff through SQL Pass-thru and SPs on the SQL Server box. It's more flexible and works for me.

>
>My question has a couple of parts. The back ground is that this system was written in FP 2.6 and taken to VFP 6.0. It is part of a 5 database system that is composed of VFP DBC and SQL 7. We have been charged with taking two of the projects written in FP and converting them to VB com based. Three of the (VFP) databases have stored procedures that are called next_id and a table that is called last_id. These tables are out of sync.
>
>1). When(or how) is this next_id fired? If we rewrite the project in VB and leave the files in VFP will the SP next_id still continue to work?
>

When do you call it? Is it set as the Default value for the field in question? If so, if you insert a record into the table without specifying a value for that field, VFP will populate it with the return value from New_ID().

Default values are supported by the VFP ODBC driver.

>2). If we take these three data bases and move them all to SQL (leaving one project using SQL, making 1 SQL DB) Then what are the gottcha's for the one VFP project that will not converted to VB?
>

Sorry. Can't help you here. If the systems are very tightly intertwined, you could have serios problems as things get out of synch. If not, you may have no problems at all.

HTH.