| david epsom dot com dot au 2005-04-05, 8:01 pm |
| > In this case, though, we're dealing with a very small number of records
> (usually < 200). When the form is opened, the total number of records
> appears immediately, indicating that all records have been brought in. the
> form is hideously slow in scrolling. Even displaying the initial of about
> 20 takes forever (about 5 seconds :-) ).
I suggest that you start a new thread with this information.
Don't mention ADP's at all. Do mention that it is SQL Server,
and that it works differently if there is no primary key defined.
'--
I'm not an advocate on the mdb/adp issue: I just don't
use adp. We have a very large application with most
customers using an MDB backend: we do the best we can
for SQL Server clients.
Record-Level locking is a Engine-level option,
controlled by Access when a database is opened:
Tools | Options | Advanced
You have obviously loaded a 'dyanaset' instead of a
'snapshot': Jet has retrieved pointers to all of the
records, and is now laboriously retrieving the data,
10 records at a time. The switch may have happened
just because of the size of the records increased.
'---
(david)
"Neil" <njones@pxdy.com> wrote in message
news:bhu4e.1036$An2.939@newsread2.news.pas.earthlink.net...
>
> In this case, though, we're dealing with a very small number of records
> (usually < 200). When the form is opened, the total number of records
> appears immediately, indicating that all records have been brought in. Yet
> the form is hideously slow in scrolling. Even displaying the initial
> screen of about 20 takes forever (about 5 seconds :-) ).
>
> All this could be attributed to the MDB blues. However, as noted, this
> form has been in place for a long time without any slowness. All of a
> sudden, it started acting this way, and I can't track it down.
>
>
> Not sure what you mean by "clicking in the database window." In my case,
> the form is opened or the user specifies an option in the form and the
> recordset is reset. A dynamic SQL statement is built, and the form's
> recordsource is set to the SQL.
>
> I did try opening a DAO recordset and setting the form's Recordset
> property instead of using the Recordsource, but the results were the same.
>
>
> All locking in the form is off.
>
>
> Well, that would be simpler, of course. But there are times when you need
> continuous form view. And, as noted, it's been working fine until
> recently.
>
> BTW, since you mention those who advocate MDB over ADP, does that mean
> that you're an advocate of ADP?
>
>
> I haven't seen any places to turn this on on an application level. And
> since this is happening globally (both on the client's LAN, as well as on
> my local PC), I can't see all of the machines having that turned on. Or is
> there a global setting for the application itself, rather than the PC?
>
> Thanks,
>
> Neil
>
|