client server

[elixir_5000]

i am using vb 6.0 . and going to design a new project . the database of the project is to be kept on server machine and the application needs to run on various machines.so plz tell me should i develop a standard exe project or a data project

some one has told me that i should keep both database and the exe on the server and distributes the shortcuts of that exe to various client systems . Will this technique work . I mean can i modify the database on server thru the shorcut of exe kept on client
if not plz tell me some other way out

[Mark Gambo]

i am using vb 6.0 . and going to design a new project . the database of the project is to be kept on server machine and the application needs to run on various machines.so plz tell me should i develop a standard exe project or a data project

some one has told me that i should keep both database and the exe on the server and distributes the shortcuts of that exe to various client systems . Will this technique work . I mean can i modify the database on server thru the shorcut of exe kept on client
if not plz tell me some other way out

I normally use the Standard EXE Project for most of my DB Apps. As for distributing the app to the users, I have Wise installer script that I use to keep the app on the users machines updated via FTP. Because if a the program hangs on a users machine you may not be able to put an updated version of the program on the server.

[szlamany]

We keep the .EXE's on servers (in each building) - and have shortcuts to those.

And yes, it's a nightmare to redistribute if users leave the app open (the .EXE file get's locked).

How many machines - users? How often will the .EXE change?

[si_the_geek]

And yes, it's a nightmare to redistribute if users leave the app open (the .EXE file get's locked).

I found that it is possible to re-name the .exe while it is in this state, so you can still copy the new version (with the original name) to the server.

The user who is 'locking' it continues using the old version until they close it, but anyone who clicks the shortcut will get the new version.

[szlamany]

I found that it is possible to re-name the .exe while it is in this state, so you can still copy the new version (with the original name) to the server.

The user who is 'locking' it continues using the old version until they close it, but anyone who clicks the shortcut will get the new version.

I've found that to be true at some of my clients - I think it's based on permissions to shares and folders. I've never gotten to the bottom of it unfortunately.

I've got one client that if I rename the .EXE while someone is in it, the shortcut on the ALL USERS desktop gets all fouled up (seems like it's cached or something).