Installing Access Runtime on a SBS 2003 Server

[gavin31]

I have developed an Access DB, with a separate front and back end, that uses the Access Runtime available from the Access Developer Extensions in Visual Studio 2005.

It works fine in our HQ, and as a stop gap solution I was considering installing it on our server so that 3 guys in remote office can use it, via Remote Desktop Connection in Windows XP.

The guys in the remote office have Access on their PCs and currently have a local copy of the DB. We are trying to get them to use the same data back end as HQ, but as the Server does not have Access or Access Runtime installed they are unable to use the DB through Remote Desktop Connection.

I now it won't be that fast, but speed is not a factor. They only need to use it once or twice a day for one or two queries.

Before I rush off and install Access Runtime on our server, does anyone know

1. any reasons why not to?
2. problems it may cause?

I am not currently looking for other alternatives, as this system is going to be redesigned in the next 6-12 months. But any suggestions about installing Access Runtime on SBS 2003 would be appreciated.

Cheers

Gavin

 

[lameid]

The only thoughts I have are...

Front ends are great... They reduce concurrency on application objects. If they may connect simulataneously you may won't to consider making them use there own front end copy. This may or may not be a problem.

One or two queries? Isn't there someone who can be assigned the task of sending to an excel file? I know you were not looking for an alternative, but remote desktop to a server, why not just remote desktop to a computer?