Re: Slow ADO connection on unbound form

Put PgSQL into debugging mode and watched what happened when I moved record
to record with same form in ADO and linked modes.

Found out that each time I move to a new record in ADO the whole table is
downloaded again. With the linked table, PgSQL isn't accessed at all; the
data is client-side.

I dumped that code and am using code I got from Access 2K Unleashed, Chapter
17 (designed for Oracle, but works well, with slight modification in PgSQL).
It's quite zippy thank you. Think it's a bit faster than linked tables.

Think I'm going to create a Data Connection class from this code that can be
easily plugged into forms (the code as written isn't very modular, as most
of it is in the form's class module).

> I've got an Access XP cient app that connects to a PostgreSQL backend. I'm
> learning how to do unbound forms (mainly because of problems with bound form
> problems -- namely inability to edit or save records, even though it worked
> previously).
>
> So, using code I found in Access 2k Programming: Weekend Crash Course, I set
> one of my forms up as unbound. It works ok, but it's at least 10 times
> slower moving from record to record. The code has navigation buttons that
> cycle through a retrieved recordset. The connection to the backend is a 56k
> modem. The bound form moves between records at 1/4 sec each. The unbound
> takes at least 5 seconds.
>
> It's possible it's not great code (though it looked good to me). Can VBA
> slowness be causing this? (running a Dell with intel P-6 731mhz). I tried
> setting recordset CursorLocation to adUseClient -- made no difference.
>
> Any other ideas?
>
>

--
Randy Perry
sysTame
Mac Consulting/Sales

phn 561.589.6449
mobile email help(at)systame(dot)com