>>Exactly, then wouldn't creating those stored
>>procedures as objects make the transition. That
>>way when you transfer the database, you still
>have
>>the stored procedures as objects in your VFP
>front
>>end instead of with your database. I haven't done
>>this, it is just a thought.
>>
>
>Greg
>
>It looks 'to me' like you are combining 'apples &
>oranges'. If I read this thread right your
>talking about moving code between 3 or 4 C/S
>platforms. If this is your intention then I would
>say wait for VFP 4/5. This release will
>(supposedly) be where the real merging of the
>technologies begins (why all languages will be
>5.0). I say wait & see. I just cannot for now
>see how you expect to just move code & it will
>work?
>
>Tom

I'm not talking about moving code. I'm simply saying that if you turn your stored procedures into objects, you should be able to more EASILY move your data to the back end, that's if you want VFP to do the stored procedures as OOP and don't want to have to re-write all of your stored procedures. I'm also wondering if it wouldn't make more sense. If not, I guess you should re-write all the stored procedures in the program you're upsizing to, who knows, it was a thought? I do look forward for 5.0, I didn't hear any word on it about what you were saying, but OLE is the biggest thing I have heard.