One of the worst features of Access as a database management system is that it does not reorganise the database itself. Every time you add a record, the database gets bigger, but when you delete a record the space is not recovered so it never gets any smaller, only bigger. If you use Access for your project you must be prepared, from time to time, to download a copy of your (now huge) database and reorganise it using a local copy of Access, then upload it again.
Another bad feature that I have encountered (and ask Jac from Ingentus too) is that there is only one copy of Access running on the server, and if another site has some bad code that makes Access lock up or crash then your database is down along with everyone else's until the ISP tech support reboot the server to get it going again. My advice, if you will be changing the data much, and particularly if you are offering a service to other users who will complain whenever it doesn't work, is use mySQL or SQL Server. I would also echo the feeling that there is a fundamentally bad database design decision in having a separate set of tables for each client instead of a table of clients and one set of tables with a client key field, but I can see your valid reasons for doing it that way. You might even (with Access) have it easier using a separate database for each user (serialno.mdb) and that gives you possibilities of passwording the db or the directory it's kept in... Bj ____ � The WDVL Discussion List from WDVL.COM � ____ To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] Send Your Posts To: [EMAIL PROTECTED] To change subscription settings to the wdvltalk digest version: http://wdvl.internet.com/WDVL/Forum/#sub ________________ http://www.wdvl.com _______________________ You are currently subscribed to wdvltalk as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
