Access Database Project Help?

[Guest]

Greetings. I was trying out the ADP. Our office moved we all got new PC's.
I copied the ADP file to disk, but the tables, forms etc. do not exist. I am
very new to this, could someone explain what I should have copied as not to
lose the
ADP? It is quite different from MDB I guess.
Regards.

 

[Allen Browne]

Yes, Lin, that's a pretty good summary of what's wrong with an ADP.
You can't just copy it to another computer like you can an MDB.

The tables for an ADP reside in SQL Server (or a throttled version of SQL
Server called MSDE or whatever the flavor-of-the-month name for it is at
present.) To run it on another machine, that machine must have SQL Server
(or MSDE), with the tables, and the permissions so the server can serve it
up for Access to use.

Unless you have a particular reason to use SQL Server, you might consider
the ADP to be a marketing gimmic from Microsoft to get you interested in
their bigger database product. If you do have a need to use SQL Server, you
are probably better served to create an MDB, and attach the tables, instead
of messing with the ADP.

 

[Guest]

Thanks Allen. I guess then what to do when your database becomes to big.
Any suggestions on a new direction????

Regards

 

[Allen Browne]

What's "too big"?

Can you identify what you need that is beyond Access?

 

[Guest]

Hi Allen
I am sharing the database among 4 staff shared on the Agency I:\
There are about 300,000 client files. Growing daily. The searching is very
slow.

Regards

 

[Allen Browne]

4 concurrent users on a LAN (not WAN.)
300k records in the table.
Access should be okay with that.

Changing the back end to SQL Server probably won't make that faster.
Whichever back end you have, you will need to ensure the db can use indexes
for the search, e.g. ensure the search/sorting fields are indexed, avoid
leading wildcards, avoid VBA function calls in the SQL statement, etc.

 

[Guest]

Thanks Allen for the advice.
Regards.

4 concurrent users on a LAN (not WAN.)
300k records in the table.
Access should be okay with that.

Changing the back end to SQL Server probably won't make that faster.
Whichever back end you have, you will need to ensure the db can use indexes
for the search, e.g. ensure the search/sorting fields are indexed, avoid
leading wildcards, avoid VBA function calls in the SQL statement, etc.