jason_nevin
Registered User.
- Local time
- Today, 14:24
- Joined
- Nov 22, 2002
- Messages
- 46
I have an MS Access database where the tables are held in a backend on a file server and the forms, reports, queries, etc are held in a front-end which is distributed to each user. This has worked fine up to now.
I now have a requirement to access a number of MySQL tables that are held in a remote database. My solution to this was to introduce the database as an ODBC source (using the 3.51 MySQL driver) on each machine and link to the requisite tables from my front-end . I tested this and it worked fine. However I've now rolled it out to a few machines in our office and the users are suffering with memory problems (XP is asking them to close other applications). The users in question have 512Mb of Ram which I would have thought would have been adequate.
Can anyone explain why using ODBC would use alot more memory? Can anyone suggest an alternative way of doing this?
Thanks.
I now have a requirement to access a number of MySQL tables that are held in a remote database. My solution to this was to introduce the database as an ODBC source (using the 3.51 MySQL driver) on each machine and link to the requisite tables from my front-end . I tested this and it worked fine. However I've now rolled it out to a few machines in our office and the users are suffering with memory problems (XP is asking them to close other applications). The users in question have 512Mb of Ram which I would have thought would have been adequate.
Can anyone explain why using ODBC would use alot more memory? Can anyone suggest an alternative way of doing this?
Thanks.
