Persistent connection between FE & BE for better performance

[CB]

Hi all,

I have a question about something I’ve been reading regarding keeping a
persistent connection between the FE and BE of a split database. (I’ve seen
the info in a couple of places but most recently in the MS-Access Performance
FAQ).

The information mentions always keeping a table open. I have a switchboard
that I created using the Switchboard Manager. I am assuming that because of
the switchboard form, the switchboard table is always open. The FAQ mentions
that the presence of an .ldb file indicates a persistent connection. I
currently have my database open and see .ldb files for both the BE and FE.

Am I correct in assuming that because of my switchboard form and related
table I have a persistent connection and, thus, this will not contribute to
poor performance when I deploy the database on the LAN? (I recognize that I
may have other issues that will affect performance but I guess I’ll cross
those bridges when I get to them.)

FWIW, if I’m correct, I can’t think of how my users could lose this
persistent connection (but then I’m no expert in Access). I’ve employed USL,
turned off all menu access (from Tools\Startup), don’t allow user access to
the database window, and am considering taking advantage of shiftkey2000.mdb
that I found on the Internet to disable the shift key. Because of this, the
users must do everything through the switchboard window. I’ve even disabled
the red X on the switchboard form so they have to use the Exit button -
though I suppose they could just close Access instead.

Thanks in advance for any and all help!

Chris

 

[strive4peace]

Hi Chris,

is the table that the switchboard is based on in your FE or your BE?

if the switchboard table in in your FE, it obviously won't serve the
intended purpose

Warm Regards,
Crystal

remote programming and training

Access Basics
8-part free tutorial that covers essentials in Access
http://www.AccessMVP.com/strive4peace

*
have an awesome day
*

 

[CB]

Hi Crystal,

All tables are in the BE. My FE only has queries, forms, reports, and macros.

Chris

 

[strive4peace]

Hi Chris,

then, yes, your switchboard form should keep the connection persistent

when it comes to performance, I find the biggest factor to be the size
of your key fields -- that is why I (almost) always use autonumber/long
integer data type, which takes 4 bytes to store.

Text takes about 1 byte/character -- and 2 bytes/character if you are
not using unicode compression (set in table design for each text field)

another big factor is indexes -- if you have RI (Referential Integrity)
enforced, Access will create 'behind-the-scene' indexes -- so you do not
have to worry about those in your table design. The only indexes you
need to create are

1. Primary Key
2. Unique indexes on other field(s)
3. Index(es) on other fields to speed up searches

but -- keep in mind that every index makes it take extra time to add and
update records because the indexes need to be updated as well.

Warm Regards,
Crystal

remote programming and training

Access Basics
8-part free tutorial that covers essentials in Access
http://www.AccessMVP.com/strive4peace

*
have an awesome day
*

 

[CB]

Thanks again for your help Crystal.

My key fields are autonumber/long integer so I should be okay on that front.
My database is rather small at this point with only a few relationships so
there are few indexes. I'll be sure to keep this info in mind as the database
grows.

Regards,

Chris

 

[strive4peace]

you're welcome, Chris happy to help

Warm Regards,
Crystal

remote programming and training

Access Basics
8-part free tutorial that covers essentials in Access
http://www.AccessMVP.com/strive4peace

*
have an awesome day
*