SQL Backend with Access Front

  • Thread starter Thread starter Richard T. via AccessMonster.com
  • Start date Start date
R

Richard T. via AccessMonster.com

We are considering to install SQL Server and Access frontend on the Network.
We can have anywhere from 75 to 175 concurrent users for this application.
How can I set up SQL server as the backend and use Access as the front end
without causing application slow down and possible corruption?

Can this solution even work and if so, what steps should i take?

I believe all the users will need their own version of MS Access on their
machine, correct?

lastly, would there be problems in pushing out updates on the network for the
Access frontend or would i need to push out updates to individual laptops?

Please help, I'm struggling to come up with a good solution for 75 to 175
concurrent users.

Thanks,
Richard T.
 
Hi Richard

We have done this, with some success with 60 users. What we do is have an
update directory. and run a batch file every morning that copies the latest
mdb file before the user can access the access database.

The are many ways to link the SQL Server tables to Access. ODBC link sare
the easiest but you could program them with in each form to do the connection
at form load time.
 
I create a shortcut on each users desktop using
http://www.granite.ab.ca/access/autofe.htm

Its a free app that checks if there is a newer version of the frontend
before the program launches. It then copies the latest frontend on.

If you get the Office Developer edition, you can distribute a run time
version of access. Then each user won't need their own copy of access. The
run time version means a user can just an existing database, the user can't
create or design any access objects.

The access frontend can be adp or mdb. You'll have to read up on each.

Vayse
 
I like the run-time option. Will users be able to do any data entry on the
front end and save that data to SQL using the run-time?

Thanks,
Richard T.
I create a shortcut on each users desktop using
http://www.granite.ab.ca/access/autofe.htm

Its a free app that checks if there is a newer version of the frontend
before the program launches. It then copies the latest frontend on.

If you get the Office Developer edition, you can distribute a run time
version of access. Then each user won't need their own copy of access. The
run time version means a user can just an existing database, the user can't
create or design any access objects.

The access frontend can be adp or mdb. You'll have to read up on each.

Vayse
We are considering to install SQL Server and Access frontend on the
Network.
[quoted text clipped - 16 lines]
Thanks,
Richard T.
 
yes of course

I highly highly reccomend Access Data Projects

I've been using them every day for almost a decade




I like the run-time option. Will users be able to do any data entry on the
front end and save that data to SQL using the run-time?

Thanks,
Richard T.




I create a shortcut on each users desktop using
http://www.granite.ab.ca/access/autofe.htm
Its a free app that checks if there is a newer version of the frontend
before the program launches. It then copies the latest frontend on.
If you get the Office Developer edition, you can distribute a run time
version of access. Then each user won't need their own copy of access. The
run time version means a user can just an existing database, the user can't
create or design any access objects.
The access frontend can be adp or mdb. You'll have to read up on each.
We are considering to install SQL Server and Access frontend on the
Network.
[quoted text clipped - 16 lines]
Thanks,
Richard T.
 
Yes, all data entry will work.

Richard T. via AccessMonster.com said:
I like the run-time option. Will users be able to do any data entry on the
front end and save that data to SQL using the run-time?

Thanks,
Richard T.
I create a shortcut on each users desktop using
http://www.granite.ab.ca/access/autofe.htm

Its a free app that checks if there is a newer version of the frontend
before the program launches. It then copies the latest frontend on.

If you get the Office Developer edition, you can distribute a run time
version of access. Then each user won't need their own copy of access. The
run time version means a user can just an existing database, the user
can't
create or design any access objects.

The access frontend can be adp or mdb. You'll have to read up on each.

Vayse
We are considering to install SQL Server and Access frontend on the
Network.
[quoted text clipped - 16 lines]
Thanks,
Richard T.
 
Back
Top