Access split tables on a NAS, security settings or other network tuning

Have a split db.  Tables are on a remote NAS unit (long story.)  Performance is a bit slow.

Authenticating using NAS security (i.e. Linux NFS share) and doing well, but things seems slow.  Opening the tables locally is pretty quick, but presents the usual security warning.  Open the tables remotely from the NAS is much slower.

Properly set security in Access set to the shares (some MS security approvals need to be set in Access)?
VirtualKansasAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey CoachmanMIS LiasonCommented:
There is a lot that could be causing this:

How big are the tables?
Networking hardware
how are you linking the tables?
How long is the Path to the BE on the NAS, ...etc

Lets see if another Expert can get you a bit closer...
;-)

jeffCoachman
0
VirtualKansasAuthor Commented:
Tables are small.  Only five tables; table files size is now ~1.3MB.'s

Network is strong, but is routing through a VPN with one office in a different sub-net (tables) than the other (front end - me.)  Barracuda handling the translation flawlessly.

Tables are simply linked only way i know how; Path is \\IP.IP.IP.IP\DBTables\DBTables.accdb
0
VirtualKansasAuthor Commented:
to be fair; there are some white spaces in the actual tables file name:
actual name is DOC db Tables.accdb

Path is then \\IP.IP.IP.IP\DBTables\DOC db Tables.accdb
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

VirtualKansasAuthor Commented:
Slow behaviors are on the front end, which is unsettling given when doing something simple like modifying a report am getting the "wheel" for a short few seconds with "unresponsive" comment at screen header.  Shouldn't a report edit be a local?  Wouldn't think accessing the split tables would be part of a change like this?
0
Jeffrey CoachmanMIS LiasonCommented:
Is the front end on the users own workstation?

When you make this report change, are you moving to Report View, Layout View or Print Preview?
Moving to any of these views will force a call to the table...

Is this App being compacted on a regular basis?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
VirtualKansasAuthor Commented:
Currently I'm only user connected in this field office (both front end on my local workstation and back end tables on NAS in separate field office.)  Tuning reports getting ready to put all into production.

All behaviors are sticky with "not responding" for moments and then all is well.  Any report, form, or edit of a report or query will hesitate not responding and then go.

Have plenty of backups, so copied the back end tables to local machine and re-linked the front end to local machine and all issues went away.  Access not liking the path?
0
VirtualKansasAuthor Commented:
To be fair, maybe paranoid.  Opening tables on share is initially slow to respond in about equal time.  Just unsettling to see local front end responding slow?
0
Jeffrey CoachmanMIS LiasonCommented:
OK, then lets see if other experts chime in...
0
VirtualKansasAuthor Commented:
Working locally isn't precisely a speed demon.  Same type of delays in same fashion, just faster (of course.)  Feeling more like speed of network.  And report/query editing, etc. on Front End is almost complete; there will be no more.  On to day to day use.

To boil down the question: "is this the acceptable\best path for access linked tables"
\\IP.IP.IP.IP\DBTables\DOC db Tables.accdb

..and if so, is there some Access security settings that should be tuned for this network link to NAS back end tables?
0
VirtualKansasAuthor Commented:
You were patient, helpful & responsive and "earned" it.  Am going to call this one closed as we're going to production now.  The best thing after all the modifications, was to create a new database and import all the objects, then did decompile and recompile and finally compact & repair.  Pretty darned fast after all that, so more likely was baggage from development vs. NAS connection & speed.  We'll find out!  Thanks & regards...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.