Re: [INTERFACES] Access'97 and ODBC
От | Sbragion Denis |
---|---|
Тема | Re: [INTERFACES] Access'97 and ODBC |
Дата | |
Msg-id | 3.0.5.32.19980430083836.007f3330@MBox.InfoTecna.com обсуждение исходный текст |
Ответ на | Re: [INTERFACES] Access'97 and ODBC (Byron Nikolaidis <byronn@insightdist.com>) |
Список | pgsql-interfaces |
Hello, At 09.31 29/04/98 -0400, Byron Nikolaidis wrote: >I'm not sure why VisData still isn't able to show the index list. First of all, >I dont know what "VisData" is anyway! Perhaps you could use the odbc tracing VisData is a small tool provided with visual basic 5.0. It provides a graphical representation of all the feature of any database that could be opened through visual basic, including ODBC databases. It is quite an hard test for any ODBC driver because it tries to show *almost anything* that could be retrieved through an ODBC driver, not only data. Most ODBC drivers, even some "famous" one, fail with VisData and still can perfectly be used in normal applications. >feature (through the 32 bit odbc administrator) and send the "sql.log" to me. >Make sure it is empty before you begin your session. This will really slow >things down by the way. I'll do it ASAP, and I'll provide also the exact sequence of operation performed to show the problems. Anyway the problem showed with VisData has no importance at all, at least using Visual Basic and Access. ASAP I'll also perform some test using Power Builder, wich uses the ODBC in a different way than VB. >As for performance, the backend affects that equation greatly. You should see >what happens in Access when you are using unique indexes. Even with one keypart, >Access generates that infamous query we have been talking about (with all the >ANDs and ORs), which really slows things down. I know. Anyway I was not using Access but a small test program I wrote myself. This program perform random operations (insert, update, select and delete) through recordset opened on simple tables, so it doesn't suffer the Access "feature" of creating too complex queries. I know this is not a deep test, anyway it is the sort of operations 90% of VB code perform on databases. I think first we should obtain a functioning ODBC driver, i.e. you should continue on the way you are going now. After this we could take care of performances. Doing things in reverse order usually produce "very fast non functioning code", which is not usefull at all ;) Bye ! Dr. Sbragion Denis InfoTecna Tel, Fax: +39 39 2324054 URL: http://space.tin.it/internet/dsbragio
В списке pgsql-interfaces по дате отправления: