Excel XLSM Workbook with VBA UserForm unable to Share with Multiple Users on Network

Hi there

We created a VBA Excel XLSM with UserForm.

The issue is unable to Share with Multiple Users on Network. So i have a vba multi user form you can download the attachment, use profile :

username: Guest
Password: Guest

or

username: Mohamedk
Password: P@ssword123

Our aim is to have this workbook on our network drive (central) and users to access this

Please review and assist or fix vb code

Regards
Shabeersa

Your workbook is configured for 64bit Excel.....which I currently don't have access to cos I've left my surface pro in the hotel. This means none of your code works for me, so I can't have a proper look and don't have the time or patience to convert to 32bit.....however.....for multi user interfaces in Excel you need to have your UI workbook set as a 'Read Only' file so all users can access it. Everything the UI does is then written to whatever data source / store you're using with checks in the code to ensure read / writes succeed.

Do not even think about using Excel's 'shared workbook' functions.

@ BellyGas

Agree using Excel's 'shared workbook' is very very bad. I am having issues

Any other suggestion how to resolve this

Hi BellyGas

Any work around for my request

At the risk of repeating myself:

"for multi user interfaces in Excel you need to have your UI workbook set as a 'Read Only' file so all users can access it. Everything the UI does is then written to whatever data source / store you're using with checks in the code to ensure read / writes succeed."

could u give me an example of how to do it

For example:

Have a workbook that's saved in a network location that's accessible for all users that are going to use the system. Set that workbook to read only.

Anything that workbook does isn't saved into itself, instead its saved to whatever data store you've elected to use. Eg, if you're going to use another excel workbook as your data store then the code would first check the file it needs to write to isn't locked (ie another process isn't currently writing to it), if so wait a few seconds and try again. Once confirmed as free for use the code would then open that workbook, write / read whatever it needs to and then close it again.

Or, if you're going to use a database (Access or otherwise) as your data store then the quickest and easiest way to write to it would be by executing SQL statements on it directly.....therefore, your UI workbook (the read only one) would assemble the SQL statement to be run and send it to the database.