DataBase - Very Odd Linking issue

Asked By gcoggin
23-Sep-09 06:27 PM
Howdy,

I have two database applications that use the FE/BE model over a p2p network.
One of them works great. It loads quickly and the forms open with very little
delay.

The second one loads OK but everything opens very slowly. Even just opening a
linked table takes 6 or 8 seconds. I use some code to relink the tables for
when I am doing development. When I link to the production folder on the
backend in another folder on the same machine it takes 10 seconds and the
tables and everything open almost instantly. Ironically, the folder that
connects quicker has about 15 more characters in the path than the
troublesome one though they are same number of folders from root. The
confusing issue for me is that the same files behave so differently in
different locations.

I have checked that all the permissions are the same. Does anyone have any
suggestions for what I can look at that might cause one folder to work well
and the other one not to?

Any suggestions will be greatly appreciated.

Thanks.
Database
(1)
BEs
(1)
Windows
(1)
Recordset
(1)
Directory
(1)
Relink
(1)
P2p
(1)
LDB
(1)
  AccessVandal via AccessMonster.com replied to gcoggin
23-Sep-09 09:44 PM
Go to Tony's site on this "Access 2000/Windows 2000-Slow Performance....kind
of solved"

http://www.granite.ab.ca/access/performancefaq.htm

Taken from site.
'------------------------------------------------------------
PB stated that shortening the path from 75 characters to 31 characters and
removing four directory levels changed "from 50 seconds to load for the first
time and was accelerated to unbelievable about 15 seconds." "About 3 1/2s
instead of 15s is a real progress."  They also shortened the name of the back
end.
'-----------------------------------------------------------


--
Please Rate the posting if helps you.

Message posted via http://www.accessmonster.com
  Tony Toews [MVP] replied to gcoggin
23-Sep-09 11:21 PM
What do you mean by p2p network?  Peer to peer?  Is this in the same
office or are they separated geographically?


Are these both on the same computers?  That is the both FEs are on
your PC and both BEs are on the same other PC?


What do you mean by different locations?  Different folders on the
same server?

Now was someone else using the second slower app at the same time you
were using it?  And no one was in the first app?  If so that is the LDB
locking issue where a database variable, recordset variable or bound
form helps.  Also if relinking the tables either open a database
variable to the BE or, once you are relinked the first table, open a
recordset variable against that table.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/
  jesus replied to gcoggin
31-Oct-09 10:04 AM
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Howdy,
Create New Account
help
User cannot access linked tables DataBase I have a FE mdb stored in a Windows-secured folder. It has no local tables, only linked tables. The link points to a the front end and both back ends (the FE links to tables in two separate BEs) 2. Navigated to the secure folder. Open, modify, and close / save an excel spreadsheet in in the opening folder (a combo box that references a table on one of the BEs.) 5. Combo box generates the error stating the BE file (full URL) is either unavailable is locked for exclusive access by another user. I believe the error message is a windows error message, not an Access error message. The other BE file had not even been create* a new Excel file in that folder? I mean when you are logged in (Windows login) as userX (not as you). You need to verify that all users can create keywords: User, cannot, access, linked, tables description: I have a FE mdb stored in a Windows-secured folder. It has no local tables, only linked tables. The link points to a
Conflict Tables DataBase Over the weekend all of my backends (replica farm of 3 and 35 remote users tables don't really identify anything that is specific. Any suggestions? Mike Access Replication Discussions Windows Update (1) Access 2003 (1) MSysConflicts (1) MsysRepInfo (1) ReplicaID (1) Database (1) MsysSchedule (1) BEs (1) Mike <iatros56@hotmail.com> wrote in What about MSysConflicts? Can you delete it? It The reason listed says, "Recovered replicable data. This row was recovered from a corrupted replicable database. Verify that the record contents are correct and then reinsert the record, or delete this the star topology We did not have the problem in 3.5. I had the database up and operational since 2001. The only reason why we migrated to 4.0 was you have Jet 4 SP 6 or later on all workstations? You probably do, as Windows Update would take care of that for Windows, but it's worth a check. I've seen lots of corruption in A2K *until
SQL Server Express: Small Work Group Sans Server? DataBase Extrapolating from David W. Fenton's comments in the "Rules of thumb" thread, it seems of implementing a work group's SQL Server Express back end on a plain old Windows XP PC right in their physical area instead of becoming a tightly-controlled tenant on issues? Comments? - - PeteCresswell Access Discussions SQL Server 2008 (1) SQL Express (1) SQL Server (1) Windows Home Server (1) Windows XP (1) Exchange Server (1) Windows Server (1) PowerPoint (1) My opinion is that if the requirement can be met by is on C:. Runs almost as fast when the .MDB back end is on my Windows Home Server box. But take it into my work environment, put the back end on description of your working environment sounds like your clients are large corporations that virtualize their Windows servers and underprovision them in terms of sharing CPU cycles. Likely, they underprovision their network is SQL Server Express. I dunno, I usually push for a full dedicated box running Windows Server. it is pretty cheap to provision one with plenty of disk space and RAM
Homegrown Synchronization Followup DataBase Just a followup on how well this "homegrown synchronization" is working. It has been in there is no code in MyApp that does this). Access Replication Discussions SQL Server (1) Windows XP (1) Oracle (1) VBA (1) VB (1) APIs (1) UpdateDB (1) SyncApp (1) rdemyan too difficult. Also, now that the client has finally updated all machines and gone to Windows XP professional, speed is hardly an issue when creating the temp local copies and checking to checking for changes. So when a user logs in and connects to the server BEs, a local copy of these BEs is made. Then when the user logs out of the server BEs, the code checks for differences between the server BEs and the local temporary copies of these BEs (this is exactly what is done when a user connects to LOCAL copies of the