From: Antonio G. <aga...@ag...> - 2001-06-22 01:02:24
|
Maybe the following will contribute to the question: When we started to move applications from MS plataform to PostgreSQL. In the beginning, we did a project where we researched how to connect a MS Access client against ans PostgreSQL Server. This was because our user still want to use MS Windows, while KDE have not an Office Application that fully read and write our Word docs and Excel Spreadsheets under Linux. First we used and rewrote a tool founded in the postgreSQL web site that help to convert an Access DB to PostgreSQL. The DB convert application name is "PgUpt - postgress Upsizing Toolkit". The DB was 10 MB with more than 50 tables. We rewrote some code of this applicartion and we sucefully did the DB conversion at great Time! After that, we start to link the DB Access Client with ODBC Driver for PostgreSQL using "linked tables" and the result was very BAD. Every query taked too mouch time. Sometimes we must wait more than 2 minutes when if the same Database used MS Jet, the query was done in less than 10 seconds! We researched what is the cause of the problem., and in a book we found that "MS Access poorly interact with any ODBC driver!". If you try to get for example 10 registers then Access open a connection, get ONE register and close the connection, then again open a new connection, get the SECOND register and close the connection, etc.!!!!!! Of course if you try the same with MS SQL Server you get a better result! Well, at the end. If anybody wish to write and MS Access Client to interact with PostgreSQL using the native way. He must rewrite the app to get a better performance. I hope this will help anyone who wish to write an MS Access client for SQL-Ledger. Regards, Antonio Gallardo _____________________________________________________________ Obtenga una cuenta de correo gratis! Visite AG Software, S. A., http://www.agsoftware.50megs.com/ |