Dear All

We have an existing client who runs an Access 2 system. The system is 

large, 45 concurrent users running a single application which supports the 

clients Health Insurance business. i.e. Marketing, Adminstration, Claims 

Processing, Supplier Management.

The application is mission critical, 5 years old and creaking. Over a year 

ago the client was advised to move to an MS SQL Server back end and an 

A2000 front end. The project was split into two phases, the first being to 

port the front end to A2000.

After a not inconsiderable amount of time and effort the first phase was 

complete. However even though we converted the backend data to Jet 4 there 

were some performance issues in certain areas and the client decided not 

to implement.

As this was a two stage process we are encouraging the client to move to 

Phase 2 i.e. conversion of the backend to SQL Server but the client is 

nervous because of the experiences with A2000. We would like our clients 

to be able to see or gain reassurance from some independant sources who 

are running an Access 2000/SQL Server set up with a similar sized 

application. If any of you have an application that would fit the bill I 

would be very gratefull to hear from you.

Thanks





Mark Davies

Hi Mark



	We are currently in the process of moving to Access / SQL Server from an

ancient BTrieve database. Currently, we have an Access 97 database scheduled

to pull tables from the BTrieve database for use in an online-store

application, written in ASP (VB Script). We plan to get rid of the Access

Database once I get around to porting the store to use SQL as the backend.

	Our clients use a custom VB application to access the database. I'm not

sure what the performance gain from moving from SQL to Access was, do to a

number of factors. This was a major upgrade for us, and in preperation, we

bought a new SQL Server to run as a dedicated database server, upgraded all

of our hubs to switches (eleminating collisions and allowing the majority of

our users to run at 100 Mbps) and upgraded a number of client workstations.

	The overall performance improvement has been astronimical. In adition, we

benefit from eased Database administration, and our SQL Server opens the

door for us to do alot that our old system was inadequate for -- we're

throwing a couple of other custom apps on the network in addition to our

main one.

	You're application does sound a little two complex for Access, though it

seems every time I think that, Access continues to amaze me. I once worked

someplace that wouldn't fork at the money for a SQL Server, so I had to

force every once of power out of Access I could. The database lasted until

it hit the 1 gig point, at which time it halted with an error message (not a

nice way to come into work on monday morning).

	One cavet when moving to SQL Server, though -- Licensing. Standard Edition

is only available for less than 25 users; If you're looking at 45 Client

Access Licenses, you will have to put out the money for Enterprise Edition,

which, in edition to the cost of a database server, is well out of the IT

budget of many small-sized companies.



	--Meredith Shaebanyan

	<MeredithS@p...>



-----Original Message-----

From: Mark Davies [mailto:JMCDavies@C...]

Sent: Thursday, March 22, 2001 12:09 PM

To: Access

Subject: [access] Access 2000/SQL Server





Dear All

We have an existing client who runs an Access 2 system. The system is

large, 45 concurrent users running a single application which supports the

clients Health Insurance business. i.e. Marketing, Adminstration, Claims

Processing, Supplier Management.

The application is mission critical, 5 years old and creaking. Over a year

ago the client was advised to move to an MS SQL Server back end and an

A2000 front end. The project was split into two phases, the first being to

port the front end to A2000.

After a not inconsiderable amount of time and effort the first phase was

complete. However even though we converted the backend data to Jet 4 there

were some performance issues in certain areas and the client decided not

to implement.

As this was a two stage process we are encouraging the client to move to

Phase 2 i.e. conversion of the backend to SQL Server but the client is

nervous because of the experiences with A2000. We would like our clients

to be able to see or gain reassurance from some independant sources who

are running an Access 2000/SQL Server set up with a similar sized

application. If any of you have an application that would fit the bill I

would be very gratefull to hear from you.

Thanks





Mark Davies