|
Posted by: Bob M on 2010-07-08, 08:59:27
Instead of using MS tables, you export them, then in Access use references to the tables instead of having them in the Access file itself. Try this with a new database - Create a database table, put in a few fields of various types. Then export it, I don't know what export formats are available to you these days but I always went for DB4, just don't choose MDA or any other MS format, then delete it off the Access tables list. Now create a link to that table in Access. Write a script to fill the table up.and you will find that you have beaten the MS file size limit. Not entirely, because Access will still be deathly slow if you query large ammounts of data, so if you can keep your queries smallish. Better still, put your data into an external dataengine, such as Postgresql or MySQL, you still reference these from Access, but now Access sends your SQL to these engines and lets them do all the work. Even on a local machine it works out better, but you are now free to have the sata on another machine (server or client) and your applications on the local client. You also now have the option now to directly access the data engine from other MS Applications or your own code, independant of Access. Access has it's place, nice neat local databases, but when you reach the big time data handling it just hasn't got what it takes to handle it. |