The symptoms:
- I created a very very small MS Access DB (first one - indicative of current knowledge level).
It did what it was supposed to do, driven by menus and submenus; with forms for queries and data entry, along with options for outputs in Excel and printable matter (wow was pretty proud until...)
Performance was perfect, form loads took milliseconds.
Placed this DB on a shared network resource local to me (same building) still worked just fine.
Test subject at a distant location found the performance to be horrible
Discovery and attempted solutions:
- I had the test subject disable her real time virus checking software - no improvement.
Measured network latency found mine to be <1ms and theirs to be <35ms. I didn't think this was much to be concerned with but this is the first question...Is it?
Reason for me asking - I read a white paper with regards to this and MS's behavior when opening and editing Office application across a network where packet sizes are generally 4k making latency an issue; however, the study failed to mention if MS Access was considered part of Office and subject to the same 4k packet size.
I separated the front end from the back making the table (THAT ONLY HAS 20 RECORDS IN IT) the only item on the shared network resource - problem persists.
I had test subject copy a full blown version to her laptop and it worked perfectly.
Had support center folks provide network optimization software to her laptop with no visible improvement
As a full blown version works on hers is the solution to provide her/them with a full blown copy and create VBA code that force replicates this DB when opening and maybe closing the DB?
Or, would a better solution be to use the DoCmd.TransferDatabase when opening and closing the DB?
Thanks in advance