Hi,
I can understand why you didn't mention that before: you realise
that no-one else would inflict that structure on their clients :~).
I like to be different

Anyway, fast WAN, small database, currently in prototype status hence
everything on the server...
I am really just exploring this to expand on my (lack of) knowledge.
Use Terminal Services or Citrix or IIS or some other service
that allows you to run both the FE and the BE on the server.
If your WAN is fast enough and your users are slow enough to
let you use a BE file on a WAN server, at least put the FE on
the client machine.
Looked up CodeDb.
This could be solution by just having the relevant "library" on the
client PC - could come in handy - thank you.
If you are sure that you are going to be the exception that
tests the rule about never running Access over a WAN, then
boost up the size of the Jet cache and the Jet paging interval.
You don't have to send data over the WAN if it is in the Jet
Cache.
Now this is probably the most interesting part.
1) I gather there is no way to use a memory resident recordset as a
recordsource (which would explain why I found a site selling a COM
add-in that allows doing just that with ADO).
2) If I understand this correctly, then increasing the cache will keep
the data "locally" and any reference to the original tables will
actually access memory. Since I don't change any data, network traffic
would be minimal. This would therefore also be a good solution for a
slow LAN. I will look this up (presumably a Registry entry?). Is there
any (simple) way of checking how much memory is being used by the
different objects and how often the remote objects are accessed?
Regards,
Andreas