I have (for reasons of my own) a RecordSet Generated on one machine. I would like to be able to send the RecordSet to a client application, elseware on the network.
Both applications are VB6.
I do not wish to send the SQL to "recreate" the recordset, but the recordset itself.
Is there a way of doing this?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
There are more elegant solutions, but they are of a higher level of complextity and not for the faint hearted.
Solution 1.
You used the phrase "client application" in describing the recipient of the data in your question. The solution that this suggests is to make the "sending" application a remote ActiveX server that the client application communicates with via DCOM. This is not that difficult to set up, but will require that the IP address of the ActiveX server application machine be configured in each client machine. The server application could also (but does not have to) run under M-T-S.
In this solution the recordset could be passed as a property from the server to the client. It would be better to translate the recordset into a string property (less overhead).
A simpler form of this solution would be to place the ActiveX server application on each client PC and eliminate the need for DCOM and peer-to-peer communication. This keeps the recordset generation code in one application and locks the code away from other developers.
The determinig factor for local or remote use of the ActiveX server is the number of machines you want to actually query your database.
Solution 2.
Use the Microsft Winsock Control or another third party control to establish direct peer-to-peer communications between the two applications. This can be fun, but is not easy, as it reqires you to define the converations, allow for multiple clients connecting to the one server, etc. Definately very complex.
--------------------------
Unless you have a good reason to have only one PC querying the data, the best (read simplest) solution is the locally installed ActiveX Server or even creating it as an ActiveX DLL that is used by the client applications.
Creating a local DLL or Server is not difficult, and allows you to centralize and control sensitive code.
Hope this information helps.
Hope this helps
Thanks bkthompson2112. The problem is then remote file priverlages. Your suggestions are good, but not quite what I am looking for.
kaufmam, there is a winsock connection already... that is not a problem. I had origionally considered creating a "RemoteRecordSet" class that would emulate the recordset control, but request the data over the network. Ideally there would only be a single database connection.
I am looking into DCOM now as it happens, Even though I am employed as a programmer all my knowlege is self-taught and untill now I have not had enough reason to look into the whole DCOM client/server thing - Or if I have, I didnt realise thats what I was doing. (Although I create ActiveX DLLs and OCXs all the time).
Although I was looking at this already, if it proves the solution (unless anyone else gives me a more specific example of how) I will award you the points.
Dentab,
Your welcome.
If DCOM is the route you want to go I would suggest that you look at creating an ActiveX DLL that will run under M-T-S. You should definately do some research and get a book (or two) as this is not easy. There are plently out there, but I would look in the indexes to make sure they cover M-T-S.
One good book I used in preparing for my MCP exams was "VB in a Nutshell" (not the current version "VB & VBA In A Nutshell")
Good luck
The best way to do that (in my opinion) is using RDS. You can find more about it on http://www.able-consulting
Ivan
Well that depends. I assume the program that makes the recordset is the server and the guy who uses the recordset is the client. Create a COM Server to create the stream as I stated above. Put the stream in a collection. The Client can then call the Server, and take what ever stream it needs from the collection.
Business Accounts
Answer for Membership
by: bkthompson2112Posted on 2004-07-07 at 06:51:06ID: 11491704
Hi dentab,
You can 'persist' recordsets.
Use the .Save method of the recordset. (You can save in XML or ADTG format.)
Send the file over the network,
then, use the .Open method of the recordset. (I think it's the adCmdFile option).
bkt