Обсуждение: Re: MS Access 97 SR-1, psqlodbc 7.01.00.06, slow perfomance

Поиск
Список
Период
Сортировка

Re: MS Access 97 SR-1, psqlodbc 7.01.00.06, slow perfomance

От
wsheldah@lexmark.com
Дата:

This is because of the way Access works, and the way it tries to be extra
friendly.  When you go to change the text box source, it wants to contact the
back end so that it can get a list of valid choices for you to choose from, and
to validate your choice so you don't type something in that's going to fail.
The way to eliminate the wait is to use an unbound form.  This means writing
some VBA code that will run whenever the form info needs to be saved (user
clicks save, moves to another record, etc.).  The VBA code needs to cycle
through each of the fields, get the values, and update/insert them into the
database.  There's lots of sample code floating around for doing this, in books
and articles.

The extra code will seem like a pain at first, but it will make your app. run a
lot faster.  This is how Microsoft and other Access developers recommend using
Access in a client/server environment.  All their examples use SQL Server as the
back end, but in principle, just read those articles and substitute PostgreSQL
for SQL Server and the principles will apply just the same.

Also, you might notice that by the time you get done unbinding all your forms,
it's starting to be structured more like a web application.  So doing this might
even lay the groundwork for making it web-based and leaving Access behind
altogether!  :-)

--Wes Sheldahl




Jüri Fjodorov <jyri.fjodorov%nowecanspam.ee@interlock.lexmark.com> on 07/10/2001
11:18:44 AM

To:   pgsql-general%postgresql.org@interlock.lexmark.com
cc:    (bcc: Wesley Sheldahl/Lex/Lexmark)
Subject:  [GENERAL] MS Access 97 SR-1, psqlodbc 7.01.00.06, slow perfomance


hi all!



im just trying to migrate my ms access back-end to postgres. i used
pgadmin for it and now i have tables stored in postgres on mandrake 7.2
server. frontend is still ms access.(at least im trying redoing it for
postgres..)

problem is, when i do something(anything) with bounded
form/report(changing text box source, for example), access makes
connection to backend. i dont realy know what it do there as i am a
newbie at postgres, but its real pain in the butt with about 1000K
records in few tables. you see, i dont like to wait 2 mins just for
changing text box source.

i have strange feeling that its not normal and something configured
wrong. why access have to access backend all the time while i am in
form/report edit mode?

anyone can help me out?
thanx in advance
jyri


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html





Re: MS Access 97 SR-1, psqlodbc 7.01.00.06, slowperfomance

От
Justin Clift
Дата:
Hi,

Just wondering if you'd like to write this up into an article for the
techdocs.postgresql.org site, as there is a decent level of interest in
moving from MS Access to PostgreSQL.  There are a few documents around,
but nothing which mentions this from what I remember.

:-)

Regards and best wishes,

Justin Clift

wsheldah@lexmark.com wrote:
>
> This is because of the way Access works, and the way it tries to be extra
> friendly.  When you go to change the text box source, it wants to contact the
> back end so that it can get a list of valid choices for you to choose from, and
> to validate your choice so you don't type something in that's going to fail.
> The way to eliminate the wait is to use an unbound form.  This means writing
> some VBA code that will run whenever the form info needs to be saved (user
> clicks save, moves to another record, etc.).  The VBA code needs to cycle
> through each of the fields, get the values, and update/insert them into the
> database.  There's lots of sample code floating around for doing this, in books
> and articles.
>
> The extra code will seem like a pain at first, but it will make your app. run a
> lot faster.  This is how Microsoft and other Access developers recommend using
> Access in a client/server environment.  All their examples use SQL Server as the
> back end, but in principle, just read those articles and substitute PostgreSQL
> for SQL Server and the principles will apply just the same.
>
> Also, you might notice that by the time you get done unbinding all your forms,
> it's starting to be structured more like a web application.  So doing this might
> even lay the groundwork for making it web-based and leaving Access behind
> altogether!  :-)
>
> --Wes Sheldahl
>
> Jüri Fjodorov <jyri.fjodorov%nowecanspam.ee@interlock.lexmark.com> on 07/10/2001
> 11:18:44 AM
>
> To:   pgsql-general%postgresql.org@interlock.lexmark.com
> cc:    (bcc: Wesley Sheldahl/Lex/Lexmark)
> Subject:  [GENERAL] MS Access 97 SR-1, psqlodbc 7.01.00.06, slow perfomance
>
> hi all!
>
> im just trying to migrate my ms access back-end to postgres. i used
> pgadmin for it and now i have tables stored in postgres on mandrake 7.2
> server. frontend is still ms access.(at least im trying redoing it for
> postgres..)
>
> problem is, when i do something(anything) with bounded
> form/report(changing text box source, for example), access makes
> connection to backend. i dont realy know what it do there as i am a
> newbie at postgres, but its real pain in the butt with about 1000K
> records in few tables. you see, i dont like to wait 2 mins just for
> changing text box source.
>
> i have strange feeling that its not normal and something configured
> wrong. why access have to access backend all the time while i am in
> form/report edit mode?
>
> anyone can help me out?
> thanx in advance
> jyri
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly