Database Splitter

[fdespoux]

I have a database that is around 15.1 mb. It has around 11,000 records, 12 forms and 6 reports and 4 to 5 users using it at the same time from a file server running xp professional. I figured i try the database splitter since it is recommened when sharing a database over a network. But ever since i have done that the database runs very slow. When you open a form or close the main it takes more than a few seconds. Also when i try to do design changes to the front end it takes a while to load, save and close. If someone could please tell me what could be wrong or maybe i should just stick to one file and share on the file server like it was before. All the users are running Office XP or Office 2003.

Thanks.

[Scott Price]

You could try the decompile command line method. Many people have reported significant (up to 50%) size reductions and speed improvements when doing so.

On a backup copy of the database. Compact/Repair, close the database. Call up the command prompt (Start Menu>Run) and type in something like this:

"C:\Microsoft Office 2003\OFFICE11\MSACCESS.EXE" /decompile "C:\Documents and Settings\Scott\Desktop\EMHS.mdb" Where the first section between "s points to the actual location where the MSACCESS.EXE file resides on your computer, and the second points to the backup copy of the database.

Compact/Repair again after the decompile. Go into the code window (Alt-F11) and click Debug>Compile to recompile the db.

I wouldn't encourage going back to a single file situation unless there was absolutely no other option.

Regards,
Scott

[fdespoux]

You could try the decompile command line method. Many people have reported significant (up to 50%) size reductions and speed improvements when doing so.

On a backup copy of the database. Compact/Repair, close the database. Call up the command prompt (Start Menu>Run) and type in something like this:

"C:\Microsoft Office 2003\OFFICE11\MSACCESS.EXE" /decompile "C:\Documents and Settings\Scott\Desktop\EMHS.mdb" Where the first section between "s points to the actual location where the MSACCESS.EXE file resides on your computer, and the second points to the backup copy of the database.

Compact/Repair again after the decompile. Go into the code window (Alt-F11) and click Debug>Compile to recompile the db.

I wouldn't encourage going back to a single file situation unless there was absolutely no other option.

Regards,
Scott

Thank you for replying so fast. I did what you suggested to do but the database is still the same size at 15 mb.

[Scott Price]

You did the decompile on the front-end db where the code resides, right?

There are a number of reasons for poor performance in a database, not least of which is un-optimized code and queries.

However, in this case I suspect it's not because of this, but rather could be a potential network issue. Things as innocent seeming as the RPM speed of the hard disk on the server (where the back-end .mde file resides) can affect this as well.

Unfortunately, without knowing more about your setup I can't give more than general ideas and recommendations :-(

Regards,
Scott