You've answered the most critical question... I can't use MS Access for cross platform deployment. Having them on separate machines (if it works) could be one way of doing it, but in my eyes it's not a good solution. (too many "links" that can be broken)

Ideally, I would like to deliver the application + DB as one package, and the only thing the customer has to do is to install the software, set up the DSN (I guess they don't have that on Unix...) and then run it... voila... up and running. I guess this is my picture of a perfect world. :)

Thanks Harish for spending your time to give me an answer on this issue!

Regards,
Gert
----- Original Message -----
Sent: Monday, February 04, 2002 2:39 AM
Subject: Re: Deployment of servlets & database

There is no MS Access on unix platform ( or any other non MS OS ) , so bundling MS Access along with ur app, will restrict ur clients to use windows. One way to overcome this issue is to install MS Access on a windows m/c in the network, and ur application from any other m/c can remotely connect to DB using jdbc2.0 APIs. ( I am not sure that MS Access can be accessed across machines.. experts can throw light on this!!!!! )
 
Harish
----- Original Message -----
Sent: Monday, February 04, 2002 12:42 PM
Subject: Re: Deployment of servlets & database

Hi Harish,
 
But if I want to bundle the MS Access database with the application, (for easier deployment, since it's going to be sold as a module) is there an issue of it being developed in a Windows environment? Or do I have to build a database on each different potential platform? I'm really a beginner when it comes to moving databases between different platforms, (as well as on doing stuff with JDBC) so just bare with me. :)
 
Best regards,
Gert

Reply via email to