Network Deployment

[me1258]

I have a small access program that I need to put on a network. It will only have one user. The Network administrator insists that the DB be on the server for backup. The DB will have about 25,000 new entrys each year.
There are only 2 forms. Data entry with several combo box's and a maint. screen.

What is the best way to do this? I tried Splitting it with the wizard in Access on my home network but it is extreamly slow. I dont know if it is my cheesy home network or what. Will this work better on a real network or should I be doing something different

Thanks

 

[Kraj]

Chances are it will work better on the work network. But honestly, if you truly are the only user of the database, I don't see why you couldn't work with it on your own pc and then copy it to the network drive at the end of each day. I have never worked with Windows Task Scheduler, but I believe you can use it to automate things like this.

 

[me1258]

Chances are it will work better on the work network. But honestly, if you truly are the only user of the database, I don't see why you couldn't work with it on your own pc and then copy it to the network drive at the end of each day. I have never worked with Windows Task Scheduler, but I believe you can use it to automate things like this.

I will not be the one using it. The user will not be involved in saving the info to the DB on the server. Could I set it to syncronize once a day or something?
The easierst way to do it .... I think is with the splitter but I am concerned 2 years down the road the DB will be to huge it will take forever to run.

Thanks again

 

[Kraj]

To answer your first question: You should be able to, but again, I've never worked with it.

To respond to your second part, I agree this splitter is better. There are a couple things you can do. One is to run Compact/Repair on exit (Tools-->Options-->General-->Compact on Close). That is the simplest way to minimize the size of the database. Another option would be to write an archiving routine that runs a set of queries to move older records into archive tables, which will speed up the database performance. Althouhg if your database is as simple as you say, I wouldn't think there'd be an issue.

 

[Kevin_S]

me1258 -

Please do not double post - if your looking for assistance and the topic has not been answered in a few days simply post to it (say bump or something) and the post will pop back up to the top of the list. Double posting eliminates help you can receive because members who help on different threads would be more suited to see if something has worked or not previously - thereby increasing the amount/level of help to you and by not wasting their time...

Other Post

Thank You,
Kevin

 

[me1258]

oops

me1258 -

Please do not double post - if your looking for assistance and the topic has not been answered in a few days simply post to it (say bump or something) and the post will pop back up to the top of the list. Double posting eliminates help you can receive because members who help on different threads would be more suited to see if something has worked or not previously - thereby increasing the amount/level of help to you and by not wasting their time...

Other Post

Thank You,
Kevin

Yes...
Sorry...when I hit post the first time I got a windows error that booted me off the net....I didn't see that it had gone through because it did not pop up on the top of the list.
I will be more careful
sorry again

 

[Kevin_S]

not trying to scold you... just trying to point out the reason/benefits for not posting!

Kev