Bob (and Peter),

I *do* think that this idea is worth pursuing and creating a wish document for. Always have.

I like too the additional ideas you have for it here, Bob.

I see this as THE logical continuance of what was started as the original idea for "SET ENGINE TO. . . ".

I diverted from that to pursue my long-standing wish for the Fox Server Edition that never happened. This thread is that diversion.

While of course I don't (can't anyway < s >) object to continuing this SQL translation idea here, it might well be more beneficial to do so in another thread.

I hope that someone will take up the cause and ultimately formulate a wish document for it.

I do believe that ANYTHING (reasonable) is doable, and this is reasonable to me.

Cheers

Jim


>>Peter and Jim,
>As you know, I am a fan, of the basic concept here, but it appears that that we are actually running into either a stumbling block or a brilliant idea.
>
>Something was said about transparent, and the ability for the old style programs to use the functionality of SQL server.
>
>I think this goes back to what I either thinking, or writing on some time ago.
>
>Something like a few new commands... (lots of work by MS) but for us. just a few new ones.
>
>Set session to remote myremoteserver && which is defined in the dsn
>or
>set session to local && to cancel it.
>
>if you issue a create table with session in the remote state, it creates the table on the sql server, modi table does the same thing.
>Everthing as much as possible works with the same VFP commands.
>While in the remote session mode, you could say.
>create table local d:\mydatafile\mydata.dbf if you so wanted. but the session is scoped for remote tables.
>
>Once table are created, then using tables (backend and transparent to the VFP Coder ) would be all the approiate sql statments.... Translated.
>
>now here is a thought. Some of us more advanced user of client server applications would love to hack into those translated commands sometimes, and tweek them even more. So I would hope that there would be a behind the sceens session long of every sql stament made to the server. which could be opened up and cut and pasted into code if and or when necessary.
>
>Management of tables (remote tables) would use a similar if not the same syntax as vfp's syntax, index on tag...But actually it would send the sql - converted statment to the attached server.
>
>From working with Sql Like I said earlier, there would be somethings which don't translate exactally, or would have to added to sql tables to get them to work the same..(deleted records )
>
>But this is do able. and Worthwhile.
>
>Keeping the best of VFP powerful cursror based language, and adding a subset of transparent sql conversation translators, to handle the bolting to process.
>
>
>Even tho I have already done much of this work (for my own apps) can you imaging, issusing a commad like
>dele next 20 and having VFP translate that to whatever it needs to, to send the sql stament to the server. ? Its very possible.
>
>Now the bennifit of doing this, for the developer is tremendous.
>
>
>Bob Lee