Question Runtime Application Question

[jmischel]

I am new to distributing applications via the Developers Toolkit. I used the Package Solution wizard, created the setup files (including the runtime files) and distributed it to a couple of users withing our company. The problem I am having is that the packaged database exists on our network drive but when I deploy the application, it only updates data on the users local drive. How can I package the application so that it looks at and updates the database files that are on the network drive? Are there settings within the packaging wizard that allow for this or am I asking Access to do something it is not meant to do? My desire is for User A and User B to each be able to update data on the networked database from the runtime version of the application.

I hope I am not asking the wrong thing of a packaged solution.

Thanks,
Jason

 

[boblarson]

Once the files are in place the first time, you just send them an updated frontend file (or use one of the many free auto updaters - like the one on my website). The backend database file when put in place originally should not be having the packaged solution updating it. You would need to either work on it directly, or you can use something like the backend auto updater that I have on my site as well.

But if everyone is on the same network then, unless you have new ActiveX controls to register or other support files that weren't originally included, you just give them a new copy of the frontend and be done with it.