![]() Since SMB is also the protocol that implements file sharing through Windows Explorer, you should be able to use Explorer to look at those files directly and exercise the same protocol. ![]() The BE is on a passive file server so the only thing that would delay the operation is a delay to SMB (Server Message Block) protocol handshakes. Everything in the FE is local so the only thing that CAN cause a delay is FE/BE communications. And non-pass-thru queries that involve the back end are in an environment where your local machine's copy of MSACCESS.EXE (the Access executable image) is in control of everything. If you have an Access Front End and an Access Back End, you cannot be using a pass-thru query that would possibly lead to you waiting for the query to run in the active back end - because you don't have an active back end. Is it possible any of these little issues could cause the Error 3531 mentioned above? The strange thing is it is they say it is happening to all of their mini-applications, not just one. I'm inclined to propose rewriting the application from scratch and porting the old data over. However, I don't know what happens when they enter data directly into a query (their normal). I've checked the record locking, and it is set to no locks. We actually had the error today when opening one of the databases. It turns out they were having that error before I split the DB, and I wasn't aware. They still want to retain the ability to go in and modify things as they require. They did an OK job (it is working, for now), but after seeing them in use today, I see several things I wouldn't do, such as spaces in field names, users directly entering data into queries instead of forms, etc. They were created by a superuser, who is a database enthusiast. I was hired to take a few small access apps and split them. It's time to fill in the rest of this story.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |