Dear DSmith:
It is still worth trying the LBD locking solution.... Let me know if it
works!
HTH
Fred
"DSmith" <Donna[ at ]NOTSPAMres-xraynews.com> wrote in message
news:ORrC7cl4GHA.1544[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] > Name Autocorrect is off. I'll look into LBD Locking but the database is > only very slow when I go into design. It's fine for inputting, etc. > > > "Fred Boer" <fredboer1[ at ]NOyahooSPAM.com> wrote in message > news:%23WUY3S70GHA.3464[ at ]TK2MSFTNGP03.phx.gbl... >> Dear DSmith: >> >> A shot in the dark here... is Name Autocorrect on? If so, turn it off - >> that might take care of it. >> >> Another thing might be "LBD locking"... as described here: >> http://www.granite.ab.ca/access/performanceldblocking.htm>> >> >> HTH >> Fred Boer >> >> "DSmith" <Donna[ at ]NOTSPAMres-xraynews.com> wrote in message >> news:%23GZaTGd0GHA.4772[ at ]TK2MSFTNGP03.phx.gbl... >>>I have been using the FEUpdater for several years now for an Access >>>Database in a peer to peer network. It worked great until just a couple >>>of months ago. Now I can't do design work in my front end without it >>>locking up Access. If I get everyone out of it--no problem. But everyone >>>has their own front end and we are only sharing the back end. Has anyone >>>else had this problem or where to start to fix it? To my knowledge >>>nothing has changed except for Office updates. Any help would be >>>appreciated. Thanks. >>> >> >> > >
|