Hi Rocky.

I'm missing something here. What "shared library" are you talking about? It seems like every user has his own copy of the front-end, and that is correct. And they all map to your network back-end, and that is correct.

That's a great question, and you're absolutely right to be cautious about Access database corruption. The short answer is yes, you should copy the shared library ACCDB file to each user's local machine, just like you do with the front-end.

Referencing the library file directly over the network can increase the risk of file locking, performance issues, and even corruption, especially if multiple users are calling functions or running code at the same time. Access loads referenced libraries into memory just like it does the front-end, so keeping it local ensures better speed and stability.

It's also a good idea to include the shared library in your batch file or deployment process so it's copied to a known local folder like C:\MyApp\SharedLib.accdb. This way, everyone has the same version in the same location, which avoids broken references and potential locking issues. If your shared library contains only code like functions and class modules, you might also consider converting it to an ACCDE file before distribution to prevent edits and slightly improve performance.

Again, excellent question. I'll be sure to include it in this week's QQ.

Sami he's talking about the topic of this video (above). I show how to create a shared library ACCDB file that has all of your "common code" that you use with multiple databases. Like if you have a FtoC conversion function. DLookupPlus. That kind of stuff.

Thank you very much Richard!  I thought that would probably be the case, but figured I'd make sure in case there was a bit of extra work I could save myself.  But even having to make sure the library gets copied over is worth that bit of effort if it means I won't have to update the same bit of code across multiple databases.

Richard, I often forgot to look at the main topic of the thread and make myself look silly.

Rocky yeah, I'd say if it's a function that is almost never used, maybe once in a while you might be okay leaving it on just the server, but I wouldn't recommend it because if there's other code in there that is used, that whole codebase has to be pulled across the network.

Sami oh I'm guilty of this too. I've sometimes answered questions thinking it was about Access and didn't realize it was posted in the ASP forum or even the Excel forum.

Gentlemen, Great Topic ! For my own understanding you have 3 databases Front End, Back End,  Shared Library?
The Front End and the shared Library get copied to the Local machine and the back end stays on the server.
The Shared Library Database contains code and Functions so the Front End and the Back End don't get bogged down?

Thank You in Advance!!

Dave

Yeah, watch the Shared Library video (see the title way at the top?) It explains why they're handy. This way you don't have to keep copying the same functions (or update them) to multiple database.

I don't know if I should post a new topic asking for help or not.  I'm working on the shared library and it's not working.  The issue (I think) is that there's a class module in the library.  It's the error handling code from the Northwind 2.2 database.  I use it in every one of my databases, and I've started doing some light customization, so it's a prime candidate for the library.

When I open the database, it says Compile Error: Variable not defined, and clsErrorHandler in the first form is highlighted.  

I found and followed the instructions here, and either they won't work for a library like this, or I did something wrong (https://nolongerset.com/creating-class-instances/)

Any advice?  Or a more appropriate place to post this question?

I just found this site, https://learn.microsoft.com/en-us/openspecs/microsoft_general_purpose_programming_languages/ms-vbal/a09fd48e-abed-4da8-8c4c-a110bf4ef6b6 , and I made the class module "Public Creatable".  It SEEMS to have worked, but I'm going to do a bunch more testing just to be sure.  If anyone can give me a roaring "STOP" if what I'm doing is a dead end destined to destroy my soul, I'd appreciate it! :)

If it works, it works.

Only the Necronomicon can destroy your soul. :)

Looks like I replied earlier using my wrong account. Oops. I know nothing about this Necronomicon.

Klaatu... Verata...... Necktie..... Nickel........?