New database from an old one.

[XFD1048576]

Hello!

My Access database is running slowly, I am assuming it's because I have a lot of data.

I created a copy of my database and then deleted the data in the tables so that I would not have to recreate the macros or other objects again. But in the copy I made, none of the macro or tables worked so I have to go back to adding things to my original database.

Why does this not work? Is there a better solutions or articles you can link to help me?

Thank you for your time.

 

[Joe4]

Do you regularly Compact & Repair the database? That will help keep the size down and help it to run leaner.

How exactly did you copy the database? If it is truly a good copy, deleting the data won't "break" any functionality. But note that some of your functionality may require data in order to run properly.

 

[HiTechCoach]

Joe4 makes an excellent point about compating. Regular database maintenance is important for maintaining performance of any database..

I created a copy of my database and then deleted the data in the tables so that I would not have to recreate the macros or other objects again. But in the copy I made, none of the macro or tables worked so I have to go back to adding things to my original database.

Why does this not work? Is there a better solutions or articles you can link to help me?

Yes.You really should split the database into a front end (local) and back end (on server). Then you can have test data and production data. This really makes updating, testing (critical step taht is often isgored), and deploying changes much easier.


This allows you to load/stress test you application. I create a back end database for load/stress testing with a huge amount of records in all the transaction tables. This way I can properly test to see if my application (front end) can perform properly