Hi,

I have a rather 'busy' Access DB used by no more than 10 users at the mo',
it doesn't have lots of records, (under 100k), bu the user drag and the way
that the tables get their data for queries means I am thinking of using SQL
as a back end.

As I have over 100 forms, 250 reports and quite a lot of code I am not to
keen to start from sractch..however, would this be the best bet in the long
run or can access REALLY be a front end to a SQL database. I want to end up
with about 40 concurrent users with results being brought back in about 2
seconds max. Records wil grow to about 150k over time...

Any thoughts folks?

Many thanks,

Vince

Since you already have a substantial investment in the Access
front-end, especially with all those forms and reports, I'd recommend
sticking with it. You'd be hard pressed to re-create all of that using
VB, and you'd need to learn to use another report writer. However, in
order for your app to be efficient in supporting more concurrent
users, you need to take a long, hard look at how your forms are
working with data. Techniques, such as binding forms and combo/list
boxes to entire tables, that have little impact in an Access/Jet app
can really bog down the server. You can probably re-work your existing
app to fetch only needed data, use stored procedures for reports, and
take advantage of other SQLS features with far less work than redoing
it all from scratch.

-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446

On Thu, 3 Jul 2003 17:15:03 +0100, "Vince" <NOSPAM (AT) dial (DOT) pipex.com>
wrote: