|
| > If you open your linked view in the database window.
> you will see the row pointer, and, eventually, the total
> number of records, updated continuously as Access gets
> the records.
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.
> For a start, try using an ADO or DAO object instead
> of the Access Application object (clicking in the
> database window is equivalent to application.DoCmd
> or application.OpenQuery)
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.
> Another thing you can try is 'record level locking'.
> Turn that off if you can: I've noticed an obscure effect
> on ODBC transaction handling, which indicates that
> the connection is subtly different when this option
> is selected.
All locking in the form is off.
>
> Regarding ADP vs MDB: it is only fair to note that those
> people who advocate MDB over ADB would not in general
> countenance the opening of a view in datasheet view
> at all. Accepted wisdom is that, as when using a bank
> ATM, the user should request only one record, and only
> the requested record should be displayed.
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?
> BTW, a classic cause of the kind of behaviour you are
> seeing is ---- inadvertent SQL or ODBC logging ----
> Check that you haven't accidentally left logging turned
> on somewhere :~(. The Jet settings are TraceSQLMode
> and TraceODBCAPI: there are more places to turn on
> tracing in your ODBC DSN etc.
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
>
> (david)
>
>
> "Neil" <njones@pxdy.com> wrote in message
> news:Mt30e.2142$H06.318@newsread3.news.pas.earthlink.net...
ed","JIT","MImage","HImage","AdCode","OnWeb"[color=darkred]
d","JIT","MImage","HImage","AdCode","OnWeb"[color=darkred]
>
>
|
|