Working with several stations

[galar]

I know that all the rules say that when I have a server and several stations, I need to keep my front-end application at each station and the back-end at the server.
However, it's very difficult to update the client when I have made changes to my program and I want to upgrade him. I need to go to each station and replace the file.
I have a client with 12 stations and their technician had refused to work this way. He convinced me to have a try and to put front-end application on the server too - this means that each station has a link to the front-end and several stations using it at the same time. I gave it a try and I have people working this way for several month already.
The question is, whether it's possible to continue working like this and if not then why? What are the possible problems that can arise by working this way?

Thanks in advance

 

[smedvid]

Why not develop an Auto-deploy mechanism that can sense when someone is out of sync? I have a programmer that recently created something very nice that prohbits the Access app from launching until the user has upgraded. He used an Install-Shield clone to have a nice Setup routine that insures the desktop/directories are the same one each workstation... htwh Steve Medvid
"IT Consultant & Web Master"

http://users.erols.com/medvid/

 

[Junior1544]

well, why not use a script... the user will execute the script that will copy the front end to their local hard drive, then execute it... that way they will still be running localy, but any time you make a change on the one on the network, and user that goes to use it next, will automaticly get the new vertion... the only limit i can see, is having to many people sharing the same file... so if you have more then 4 or 5, i would suggest using the script to do it... it's easier, requires no user intervention... and will be easier on the server then all the users constantly using the vertion off of it's hard drive...

--Junior Junior1544@yahoo.com
Life is change. To deny change is to deny life.

 

[galar]

Thanks to both of you.
I think that I can make some batch on each station which will copy the fron-end from the server - I didn't think of it.
And, Junior, you've wrote that I should make a script - this leads me to another question: I know how to make batch files, but what do you mean when you say script? Do you mean HTML file with VBscript or it's something else?

Thanks in advance.

 

[Junior1544]

i was thinking of a logon script myself... but a batch file would work fine... that'll update it each time they load it, even if they didn't logoff... you just need to watch in a batch file that it closes right...

gata go, ttyl...

--Junior Junior1544@yahoo.com
Life is change. To deny change is to deny life.