Slow Program

[aw23]

I have a huge access program with a database with several tables one of which has 30,000 records. The program has slowed down significantly and I'm trying to figure out how to speed it up. I have just added 20,000 of the 30,000 records. WOuld this be the cause? What can I do to figure out the cause and then speed it up? I am looking for a starting point as I am not sure what to look at.
Thanks in advance for any ideas.

 

[aw23]

I have now downloaded the FE to all users pc's. My question is this. Eveytime I update the program I put the new version on the network. Is it possible to create an exe which will automatically replace the users local copy with the file on the network (Everyones path is the smae on the local so that one exe would work for everyone). That way every user can update their file on their own by running the exe at their leisure.

Thanks

 

[Craig0201]

Yes.

Very simple. Use the FileSystemObject to compare dates.

Have you also moved the backend from your PC to a server?

 

[aw23]

We don't have a server here, it's a fake network. So all users are still running off my computer.

 

[aw23]

I need to create the exe in vb, right? No other options? I don't have VB installed on my computer,hmmmm...

 

[PHV]

You may write a .VBS script.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[aw23]

I know nothing about this. Would you be able to start me off or reccomend a link where I can read?

Thanks

 

[PHV]

Take a look here:

http://www.msdn.com/scripting/

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[Craig0201]

Running off your computer is the prime cause!

You working on it will have priority over network requests. Hence slow speed.

You need to find a machine, even another desktop, that is dedicated to the task.

 

[aw23]

I just spoke to our tech guy. I asked him if that is the cause and he replied that since I am not running anything heavy on my machine, it will not slow down the application.

 

[TomHW]

I use a combination of batch files and shortcuts to allow the users to automatically update to the new version every time they run the program. The user runs a shortcut on their computer, which runs a batch file on the server which checks if a new version is available. If it is it downloads it and runs it. If the user has the newest version it just runs that.

A pretty good explanation and example of this is located at:

http://www.abcdataworks.com/deploy.htm

It is a fairly easy setup and very simple to do.

 

[1DMF]

I do it in a similar way - every employee has a Z drive. which is where they run a local version of the DB.

on the server I have a batch program i run which copies the new version to everybodies Z drive.

I have to send a global "net send *" to let people know they need to log out of the DB.

And remember SP2 turns windows messaging off, so the clients will need to be set up to recieve messages.

But this works very well for our environment as we only have 8 employees using the DB.