Splitting a Database

[doulostheou]

I recently decided to split my database into a front end/back end environment. What I noticed though was a huge slow down in performance. One subform in particular takes 5-8 seconds to load, as opposed to less than a second before the split.

I know that splitting the database comes highly recommended in this forum, but the slowness is unacceptable. I especially want to split the database so I can execute changes quicker.

By the way, I have read several threads that recommend turning off the name autocorrect feature. I did this in the front and back end but did not notice a diference. I also compact/repair the database regularly.

The other thing I tried was creating an MDE file, as I was told they run quicker. Unfortunately, I am told by Access that it cannot be created. I believe from what I have read that I have too many forms that have attached modules.

For now, I am going to merge the database back into one file. But if anyone could offer some advise, I would like to pursue a split again.

 

[Mile-O]

The other thing I tried was creating an MDE file, as I was told they run quicker. Unfortunately, I am told by Access that it cannot be created. I believe from what I have read that I have too many forms that have attached modules.

Your code won't compile because you probably have references to objcts that don't exist. If you, for example, add a command button, give it a Click() event, and then delete the command button the Click() event remains in the code. Any refernces like this need to be removed.

In a module, select the menu item, Compile All Modules and it will point you to references that don't make sense.

 

[doulostheou]

I could have sworn I made sure the database was compiled before I tried creating the mde, but I just tried again and it worked. I thought I read somewhere that once you had over x number of modules, you couldn't create and mde but I can't find it again. Anyway, I now have an mde file. I'll see if it solves my slowness problems. Thanks.