Hello.

I have created a persistent recordset instance to a dummytable in the
back-end database from each front end (example: 3 of them).

Without the persistent recordset, when 2 or more FE's have locked the BE,
both FE's run quite slower.

With the persistent recordset, when 2 or more FE's have locked the BE, both
FE's run at the same speed.

However, we are still occassionaly experiencing sluggish performance on some
of the front ends. There is no prediction which FE is going to sporadically
behave slowly. There is alos no prediction which action from the FE will
cause the FE to behave slowly.

Do you have any advice about enhancing FE speed, in addition to the
persistent recordset object?

--Anthony

Anthony

Our networked Access applications suffered delays after an upgrade to the
network antivirus software was installed. Just a thought...

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Anthony" <(E-Mail Removed)> wrote in message
news:ONsM$(E-Mail Removed)...
> Hello.
>
> I have created a persistent recordset instance to a dummytable in the
> back-end database from each front end (example: 3 of them).
>
> Without the persistent recordset, when 2 or more FE's have locked the BE,
> both FE's run quite slower.
>
> With the persistent recordset, when 2 or more FE's have locked the BE,
> both FE's run at the same speed.
>
> However, we are still occassionaly experiencing sluggish performance on
> some of the front ends. There is no prediction which FE is going to
> sporadically behave slowly. There is alos no prediction which action from
> the FE will cause the FE to behave slowly.
>
> Do you have any advice about enhancing FE speed, in addition to the
> persistent recordset object?
>
> --Anthony
>