Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Andrzejek on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access 2000 How to install in a Server Client Network. 1

Status
Not open for further replies.

luccas

Technical User
Dec 21, 2000
30
US
I would like to find the correct way to install Microsoft Access 2000 in a Server - Client Network.
Currently I have the data Database on the NT 4.0 Server. The Application (Microsoft Access 2000) is installed on the Cleint. The Forms and Reports Database is installed on the Client. This loads slow. How can I improve this?
 
Is this a Novell network?
How fast it it 10 base-t, 100 baseT?
How large is the database in Megabytes
Speed of the client CPU
How much RAM is in the client

All of these and a few more can affect the speed.

DougP, MCP
dposton@universal1.com

Ask me how Bar-codes can help you be more productive.
 
Also how is the data being passed to and from the server

odbc linked tables
ado
or stored procedures


Dave
dab@completebs.com
See website for more info but we can develop most things for most people.
 
> It is a Microsoft Network
> the bus speed is 100 baseT.
> The Data Database is under 9 megabytes.
> The Forms- Query Database in the Client is under 8 megabytes.
> the Client has 64 mb ram.
> The Client CPU is 366.
> The tables are linked.
>
> Should Microsoft Office 2000 be loaded on the server as well as on the
> Client?
>

I changed my Client to 128 mb ram
The Client CPU is now a Pentium 3 600

This change helped but forms open slowly.
Combo boxes are slow to load (approx. 30 seconds), but after the Combo Box
has populated it is instantaneous in subsequent records.

 
I have a similar schema as you. There are a few things that will help.
1- Make sure you have good routers. I switched from Volk 10T to 3Com Superstack II 10T and experienced a two or three to one improvement.
2- Make sure your linked tables refer to a drive and not a URL. ( Not \\computername\path\table.name but rather "driveletter":\Path\table.name .) If you are not aware of this the performance difference is quite impressive.
3- The last is the one I use although it has it's draw backs as well. I run local tables on most of my machines and synchonize the tables.
Hope some of this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top