I thought I'd do something like this:

I thought I'd use a view at the mid-tier to get the data from Oracle and send it to the desktop app. When the desktop app sends the dbf back, I create the same Oracle remote view again, and overwrite the view data with the .dbf data. Then I do a tableupdate() from the modified remote view back to Oracle. I thought this would be safe since the remote view will be pulling data from several tables at once and I wouldn't have to be concerned with the Oracle structure, etc. I was going to keep the DBC generation stuff in the init of the midtier object.

?


Something else. When the midtier object makes a .dbf, I was going to compress it, encrypt it, then filetostr it to get it into a memvar that the desktop app would read. Then the desktop app would be doing the same to move data back. Is that the fastest way to move the data, or do I have too many steps or something? I was going to require (thru DCOMCNFG) datagram UDP/IP only as my DCOM transport.

?

Thanks!

>EncodeDBF/DecodeDBF should work fine. You just have use DBF() to get the actual file of your cursor. YOu can't really use the updatable features of a view if you do it this way, so why use a view at all? I think that SPT is probably more appropriate here...


>>I have VFP as a desktop client and also as a mid-tier DCOM object. The desktop client should do a createobjectex() and in the INIT method of the remote object, a DBC and remote view to Oracle gets created. How do I get that cursor/.dbf from the remote object to the desktop client DBC, flowing over the DCOM transport (the createobjectex() connection)? Since the cursor is binary (and I intend to encrypt/compress it also), I am having a hard time wrapping my head around how to move binary data back-n-forth quickly (I can pass strings OK) through DCOM.
>>
>
to