I work as an employee in a team consist of five employees for example, each employee has their own PC. We have a shared folder containing sub-folders and files so all team member can access and use files in it . I placed the mdb file ( I named it EMP_DATA.mdb for example) on folder named "DATA" folder ( the subfolder of the shared folder). In EMP_DATA.mdb, I created a form named EMP_INPUT form that will be used by the entire team member.
I am the only person who have MS Access installed on the PC, but the other team member are still able to run MS Access application since they installed Access Runtime on their PC. The directly open the EMP_INPUT, i created shortcut in the DATA form. So far, everything was OK
But problem appears when I located the *.dll file ( to prevent mouse scrolling through records in the form) on the DATA folder, suddenly the other team member cant longer open the form with the massage "Execution of the Application will be shut down due to runtime error"
Whats wrong with this?
Kindly need your help
If you are all accessing the same MDB datafile located on the server via a shared drive/folder you should really SPLIT your database into two mdb files one with the data tables in it (backend) and the other with the rest of your objects (frontend).
You then link the tables located in the backend file on the shared network drive letter folder path to this frontend mdb file and distribute a copy of this frontend file to a commonly named folder on each of the networked PC,s. (whether this be by batch file at logon if you are on a domain or by whichever other means is at your disposal.) Each of the PC's must have a networked drive letter in common ie: Z drive mapped out to C: on the server if C: is the server drive hosting the mdb datafile.
In other words each PC has a copy of its own frontend file each one of which accesses the backend datafile hosted on the server. If necessary you can of course make a shortcut on the desktop on each pc targetting each of the PC's frontend files and thus each PC has its OWN input form if you get me.
This is standard Access methodology when in a multi user environment and you might well find that any conflicts that you have may well disappear once you also place a copy of the DLL file into the (and I am guessing at your operating path for the .dll file C:\windows\system32?) required folder on each PC. (if this is the rather excellent Stephen Leban's mousehook.dll then it can also reside in the same folder as the frontend file as well)
Hope this gives you at least some sort of an attack plan
Regards
Jim
2
