Hi
I've developed an access 2000/SQL 7.0 system which runs on two sites. Everything is fine here on the site where the server is located but the other site is connected via an ISDN line and the access speeds are pretty much unacceptable for tasks involving a lot of database access.
To ease things on the remote site I'm thinking of taking a crucial function from my access project and compiling it to a VB .exe file which I would sit on the server and call from the other end of the ISDN line - thus cutting out all the traffic across the slow connection.
What I would like to know is...
Does this sound feasible?
Is it ok to run a VB .exe on an NT4 server?
How do I call the .exe file? I want to specify a path on the domain to run the .exe and have access wait for a success/failure boolean from the function before it proceeds.
I've got to sort this quickly. Any help appreciated.
Wayne
I've developed an access 2000/SQL 7.0 system which runs on two sites. Everything is fine here on the site where the server is located but the other site is connected via an ISDN line and the access speeds are pretty much unacceptable for tasks involving a lot of database access.
To ease things on the remote site I'm thinking of taking a crucial function from my access project and compiling it to a VB .exe file which I would sit on the server and call from the other end of the ISDN line - thus cutting out all the traffic across the slow connection.
What I would like to know is...
Does this sound feasible?
Is it ok to run a VB .exe on an NT4 server?
How do I call the .exe file? I want to specify a path on the domain to run the .exe and have access wait for a success/failure boolean from the function before it proceeds.
I've got to sort this quickly. Any help appreciated.
Wayne