How To | Self Installing Access Front End File
HTML-код
- Опубликовано: 8 сен 2024
- In this video I show you one way to have your MS Access front-end check its name and location on startup and if it isn't in the right location or named correctly, install itself to the right directory with the right name.
This sample file and code, as well as all sample files sand code I use in these videos, are available to members who "buy me a coffee". If you would like to have access to these source files, please check out the link below:
buymeacoffee.c...
If you would like to check out my video on using SQL within VBA, click the link below:
• How to Execute SQL fro...
Nice approach! I built a front end/back end split solution about 12 years ago that is being used by about 100 people in 50 difference offices. This may have come in handy back in the day, but my concern has always been more with the user moving the backend database! I eventually built a version control system that uses a SQL server to check versions and then prompt the user to download new front ends. If I ever get the time to invest in my old dinosaur, I might borrow your idea to ensure that the front ends are placed in the correct location. This can even lead to an auto-updating application that will download itself and install in the correct folders.
Update the front End itself is Great idea
Thanks for checking out my video! Yes, those back end files on file shares were always dodgy to manage... corruption, tampering, moving... they were nightmares. lol
Every new database project I take on now, the data either resides on SharePoint as lists or on SQL Server.
Take care!
As usual you have demonstrated a unique topic and very well presented.
Thank you for the very kind feedback, very much appreciated!
Just what I needed
Awesome, I'm glad it was helpful!
Great tutorial. I like the pacing and the overall flow. ❤❤
Thanks for the kind feedback my friend... very much appreciated!
Hi Rich from Advantage Applications. This is Mark. I have an access database that I created last year for my nonprofit organization. I am trying to find someway to auto update my access front end to about 5 computers. My network has a fileserver that is our main computer that all our documents are in. That is where my split back end and front end is. I use my laptop to split it save it in the fileserver. how much would you charge to help me do an auto update our front end. On my end i can delete the front end in the fileserver and create the new one. Then when people open the front end on their computers it will check to see if there is an update and a pop up will come up and say there is an update do you want to update? I hope to hear back from you and discuss this matter. Thanks.
Why not use Execute instead of RunSQL command, and ditch the SetWarnings?
I've gotten unexpected errors when using CurrentDB.Execute in the past and just became used to using DoCMD.RunSql.
@@advantageapplications5712 There are a couple of (small) limitations with Execute (but also doesn't require SetWarnings), so maybe that was what caused the errors? For example, Execute cannot process references to forms and reports within its query string, they need to be included outside the query string. Also, if Execute is changing the data in the form record that is already changed, the database will show a message that another user has modified the record. The "other user" is the database engine. In that case just set the Dirty flag to false before the Execute to prevent this message.
Can i let front end file to setup trusted locations by him self?
Hmmm... good question... it may be possible but I kind of doubt it since it would defeat the purpose of the Trust Center. I doubt there would be a way to have a file make itself trusted. But I could be wrong. If you crack that one, let me know.