Need Access ADP advice

[uyuni99]

I have an old Access application that has a lot of code in forms and reports. The database is getting too large and I am thinking of moving the back end to SQL Server.

My requirements are as follows:

1. The DB needs to be multiuser and the users (3-5) will need to log in over the web
2. I would prefer not to re-write the forms and reports in ASP or some other web front end.

When I think about my choices, I see them as:

1. Have an Access ADP front end and allows remote log-in to the server where it is stored. Not sure if it is possible for 2 users to simultaneously log in

2. Distribute an ADP front end to the users, but I am not sure if it is possible to connect to a SQL Server back end over the internet, and the network traffic may be an issue.

3. Any other solution?

I appreciate all help.

- u

 

[Remou]

Also at:

http://stackoverflow.com/questions/2889946/access-db-with-sql-server-back-end

http://lessthandot.com

 

[genomon]

You may also gain some insight in the Microsoft: Access Project (ADP) Forum.

Beir bua agus beannacht!

 

[dhookom]

ADPs are not generally recommended by Microsoft moving forward. They seem to like linked tables to SQL Server. If you have remote users, I would recommend Terminal Services or similar.

Duane
Hook'D on Access
MS Access MVP