Front End and Back end Solution

Often because of network connection issues at times we lose our connection to
the back end and sometimes we have to detect and repair.

I understand my next step up is an SQL server but I am prevented from using
this. I have to pay developers for the .net solution.

can you suggest any other alternative to make the DB more stable and
stronger with multiple users accessing the database with names and passwords.

First of all, don't use wireless networks with Access backends.
The obvious solution is to get your network sorted out!

You can upsize your backend to SQL Server and still use Access for your
frontend.
You don't have to go for .Net development...

Steve

"karenp" wrote:

Often because of network connection issues at times we lose our connection to
the back end and sometimes we have to detect and repair.

I understand my next step up is an SQL server but I am prevented from using
this. I have to pay developers for the .net solution.

can you suggest any other alternative to make the DB more stable and
stronger with multiple users accessing the database with names and passwords.

On Tue, 18 Sep 2007 15:12:02 -0700, karenp
wrote:

can you suggest any other alternative to make the DB more stable and
stronger with multiple users accessing the database with names and passwords.

Check the suggestions on Tony Toews' website - he has sections on corruption
and on frontend/backend best practices:
www.granite.ab.ca/access

John W. Vinson [MVP]

Switching to SQL Server as a back end isn't going to solve your network
issues.

"karenp" wrote in message
...
Often because of network connection issues at times we lose our connection
to
the back end and sometimes we have to detect and repair.

I understand my next step up is an SQL server but I am prevented from
using
this. I have to pay developers for the .net solution.

can you suggest any other alternative to make the DB more stable and
stronger with multiple users accessing the database with names and
passwords.