-
Hello,
I've just install my new Database program (that I developed) into computer1. I'd like computer2 and computer3 have the ability to access to the progarm from COMPUTER1.
All three computers are networking, so they can see each other no problem.
This is what I did and it didn't seem to work: I went into START MENU of computer1, created a short cut icon of the program and pasted it to the DESKTOP of Computer2 and Computer3. when I click on the icon on the desktop of computer2 or 3, it could not find the program......The next thing I did was installed the program into computer2 and 3, tried to open the program by using the icon on computer2 or 3's desktop. This time it worked fine, but the only problem was it opened its own program(database) not the database from computer1.
And that wasn't what I wanted it to be. I'd like all three computers to use same database, that way, all three users will have the most recent updated data....
Any suggestions will be greatly appreciated...
Hai Lieu
-
Create a shared directory on one of the computers, place the EXE and the DB in the same folder. Make your EXE access the database that is in App.Path & "\database.mdb"
That way all users will use a single database no matter what location
hope this helps
-
I dont think a .exe should be streamed over a network.
I think that the .exe should be on the people's systems, and those systems all access "\\ntserver\database\database.mdb" or similar.
- jamie
-
How about creating an ASP interface instead?
-
'cept then you'd need a server wouldnt you ?
Or at least a system with iis on it.
- jamie
-
No!
just Personal Web Server running one of the PCs. This can be even be just a windows 95 pc
-
Of course yes.
/me hits himself in the head.
But anyway, I would imagine that windows sharing would be quicker than pws+asp.
- jamie
-
Oh yes, an exe would be faster but it all depends what sort of app it is and how much shovelling of data there will be.
I think having an ASP web front-end looks pretty smart and more , well, professional.
Whenever I write a standard VB app I'm sick of the sight of it by the time it's finished!
:)
-
Yeah I know what you mean.
But if I was writing the app, I'd have to stick with a bog standard .exe because I've never had time to look into ASP.
- jamie
