All -
I have an MS Access DB that has grown well past the point where it should be split into front end and back end. The problem is that when I split the database in two, the program runs like a three-toed sloth. Events that take 1-2 seconds when the database is not split take literally 60 seconds or more when I split the database.
Every helpful article I've read on database design talks about splitting the data source and interface, so I'm being persistent about finding a way to do this. My conclusion thus far is that either (A) I did something fundamentally wrong when I split the database or (B) The company network has some flaws that will not allow us to use a database this way.
First, I consider that I might have split the db incorrectly. I took our .mdb file and moved all the tables out into a new .mdb file. I then created links to all the tables in the front end. Perhaps this was the wrong way to do this? Should I be creating and destroying connections to the back end with a database variable programatically each time I need it?
Next, I consider that our network is simply not capable of handling this setup. We're a small company and we do not have an actual windows server, just a normal desktop dedicated to general use files.
Any suggestions on turning my three-toed sloth into a cheetah? Heck, I'd settle for a really fast giraffe at this point....
I have an MS Access DB that has grown well past the point where it should be split into front end and back end. The problem is that when I split the database in two, the program runs like a three-toed sloth. Events that take 1-2 seconds when the database is not split take literally 60 seconds or more when I split the database.
Every helpful article I've read on database design talks about splitting the data source and interface, so I'm being persistent about finding a way to do this. My conclusion thus far is that either (A) I did something fundamentally wrong when I split the database or (B) The company network has some flaws that will not allow us to use a database this way.
First, I consider that I might have split the db incorrectly. I took our .mdb file and moved all the tables out into a new .mdb file. I then created links to all the tables in the front end. Perhaps this was the wrong way to do this? Should I be creating and destroying connections to the back end with a database variable programatically each time I need it?
Next, I consider that our network is simply not capable of handling this setup. We're a small company and we do not have an actual windows server, just a normal desktop dedicated to general use files.
Any suggestions on turning my three-toed sloth into a cheetah? Heck, I'd settle for a really fast giraffe at this point....