Yes, the file (preferably the .mdb file in wich the routine is called) should go to a prefixed place.
This is the situation:
My Acces-application is used by several users, each having their own stand-alone-version at dislocated places. To help/service them, they each have their own subdomain on my website, to wich they can upload their version of the application. In this way I can evaluate what their problem is and do updates. This is of course also a way to back-up.
This procedure is at present performed by calling ws-ftp, wich has for each of the users their user/pass pre-installed. But even though this is a fairly straightforward procedure, it still proves to be too complicated for some users.
That is why I want to fully automate this process: click=upload.
So yes, most of the data could be hard coded in each users version of the application (there aren't that many of them) or maybe taken from a table in wich they are stored.
Downloading is much simpler, I put the file in an windows-installer-wizard, wich the users can just open by clicking at the apropriate link in an email I send them.
Hope you have a better view of the probem now.
hope to hear soon,
Chris :)
This is the situation:
My Acces-application is used by several users, each having their own stand-alone-version at dislocated places. To help/service them, they each have their own subdomain on my website, to wich they can upload their version of the application. In this way I can evaluate what their problem is and do updates. This is of course also a way to back-up.
This procedure is at present performed by calling ws-ftp, wich has for each of the users their user/pass pre-installed. But even though this is a fairly straightforward procedure, it still proves to be too complicated for some users.
That is why I want to fully automate this process: click=upload.
So yes, most of the data could be hard coded in each users version of the application (there aren't that many of them) or maybe taken from a table in wich they are stored.
Downloading is much simpler, I put the file in an windows-installer-wizard, wich the users can just open by clicking at the apropriate link in an email I send them.
Hope you have a better view of the probem now.
hope to hear soon,
Chris :)
Comment