Okay - I have a tough dilemma.  We are planning to upgrade the DBServer.exe from 3.x to 4.x for our clients.  Then, our application running the 3.x client needs to access the server and
download an update file stored in a blob field in a table on the server.  Then the client app will kick off the new setup.exe and exit gracefully.  The setup will drop the new client app exe and
the user can start it back up.

The problem comes from my client app is on 3.x dbisam connected to remote server.  I cannot connect to the new dbisam 4.x server so my automatic update fails.  This is not good since we
have clients with 40 to 50 workstations running our app and now they will have to manually update the client by either mapping to the server folder and running a setup.exe or copying the
setup.exe to a cd and updating all the clients.

Any ideas on how I can get the 3.x client to talk to the 4.x server over remote connection - we don't want to have clients map a drive and use fileserver mode to access old 3.x version of
the table with the exe in the blob field if we can help it.

This could end up being a nightmare for our support reps!  Any ideas/advice would be greatly appreciated!

Mike

Michael,

<< Okay - I have a tough dilemma.  We are planning to upgrade the
DBServer.exe from 3.x to 4.x for our clients.  Then, our application running
the 3.x client needs to access the server and download an update file stored
in a blob field in a table on the server.  Then the client app will kick off
the new setup.exe and exit gracefully.  The setup will drop the new client
app exe and the user can start it back up.

The problem comes from my client app is on 3.x dbisam connected to remote
server.  I cannot connect to the new dbisam 4.x server so my automatic
update fails.  This is not good since we have clients with 40 to 50
workstations running our app and now they will have to manually update the
client by either mapping to the server folder and running a setup.exe or
copying the setup.exe to a cd and updating all the clients. >>

I must not be understanding what you've said correctly, because I don't see
the problem.  The version 3.x client will access a 3.x database server,
download the update, terminate itself and kick off the new setup, and then
the new setup will install the 4.x version, correct ?  Where is the conflict
?  You will have to run both a 3.x server and a 4.x server in such a
scenario, but that's not a killer since you can have the 4.x server either
run on a different set of ports, or on a different IP address with the same
ports.

--
Tim Young
Elevate Software
www.elevatesoft.com