Hi, I need help please. In runtime mode I am trying to open data ms base B (password protected) from ms data base A. My code fails in this line: Set appAccess = New Access.Application. Thanks.
Hi Richard, one point that's important for new Access users to understand is that Access 32 bit runs fine under Windows 64 bit, but of course not vice versa. Personally, I run Windows 64 bit, Office 365 64 bit and 32 bit Access. I hope it never becomes necessary to migrate to Access 64 bit.
Yeah, I fought the 64-bit upgrade myself for YEARS. Even Microsoft recommended (at the time) that most users didn't need it. However, since it's now the DEFAULT installation for Office, and most users are getting 64 installed unless they manually change it, I decided it was time. See 599cd.com/32v64bit
Richard: All I need to distribute a module that I wrote in Access 365. It has no database other than the ACCDB that holds the module. How do I point my runtime to the ACCDB that contains the module?
This is great! I thought I have to re-create my database by using another platform. They don't want to get an ms office and I'm almost done with the DB. You saved me a lot of time.
Desktop application . Split database. How to install on client computer with run time with automatic location getting? Thanks in advance. And thanks for very good presentation of access. I show many videos of your and Steve Bishop sir. And now I completed my application of accounting with GST for all India in access 2021. Thanks and obliged❤❤
I've never used runtime because of the need to re-distribute the runtime every time it is changed and the potential need to troubleshoot different client-side issues for different users, which could be pandemonium. A web interface would be much better because the admin could update web code on his end without his users having to do anything other than refreshing their browsers; and all issues would be likely server-side only and easier to manage.
Indeed. However, Access doesn't have a web interface. If you want an Access-only solution, then the Runtime works just fine. I've been recommending it for... Jeez... probably 20+ years now. Since before it was even called the "Access Runtime." It used to be the "Access Developer Extensions" back in Access 95 / 97 / 2000. LOL. Updating the end-users with a new front-end is a piece of cake: 599cd.com/Updater
In access 2021 runtime there is condition that client has which version of Ms office.. The runtime install only that version of runtime. So if your client has Ms office 2016 the runtime will install access 2016. So your application developed in 2021 can not work.
Thanks Rick, great info. Just to verify...if I distribute ACCDE file to users who have the full Access program they can't get in and tinker around with my database. They would have to have access to the ACCDB version?
Thanks so much sir for your help. Following your tutorials I have built a database with forms in MS Access. However, I need to run the Front End on 8 different kiosks running on raspberry Pi which has just LibreOffice. Please is there any way I can do that?
Another great video, thanks Richard 👍👍. I wish I had found your channel years ago. I created and have been developing an application that originally started life in Dbase III Plus 25years ago. I recently updated my application to 64bit because across our organisation we are migrating to Office 365. I have a few remote users that are still running 32bit Office for other compatibility with other legacy applications. I'm not willing to continue developing different bitness versions of the DB, so these guys are stuck with the last 32bit version that I distributed to them. Can I install the 64bit runtime on their computers with 32bit office? Also, the DB front end checks that the back end is in the default location before it fully loads. If it isn't then they can browse to the location of the back end and relink to that location. Would this scenario work if I convert the file to an ACCDE file before distribution?
No, you cannot have different "bit-ness" versions of Access (runtime or otherwise) on the same machine. I cover relinking tables here: 599cd.com/Relink. The extended cut includes code to auto-relink, and yes, it will work in an ACCDE. Time to join. LOL
Richard, thanks very much for this instruction video. I have successfully set up an application to run under the Access runtime setup. The only problem we are having is that we can't get it to print out. This works fine on the full Access developer but not in the runtime version. We get error messages and it shut's down, presumably because the VB part crashes. Is this something that you have come across ? We're happy to join and pay you fees if this is the only way we can get this sorted. All the best from Chester, UK. Mike J
Hi Mike. I've never come across this issue before. Sorry. Give it a Google search and see if anyone else has. Also, my memberships are not for troubleshooting. I don't offer consulting services or fix databases. I teach "how to" do stuff. Good luck.
If you want to distribute a database and and let the customer run it with runtime on a single desktop. How do you relink the front end to the backend when the user does not have access to the menu's in Access?
You make sure the tables are linked properly before you distribute it, and they're pointing to the same backend location. I recommend a shared drive letter like Z:\Database but a share name will work like \\SERVER\Database
@@599CD Do you have a lesson showing how to do this in code. The people I am helping have no idea how to setup a shared drive and are too far away for me to take the time to drive to them especially since I do not charge them in the first place.
That's more of a networking issue than an Access issue. Sure, I could show you how to relink to the tables in VBA if you enter in what the shared drive is, but if they don't have a network set up already with a shared drive established, that's not something you can easily do from Access.
Yep. That's a risk you take with Access. People need read/write privileges to the back-end folder. If they know what they're doing, they can open up your tables directly, or even delete the database file altogether. There's not much you can do about it. That's why you need good nightly backups, saved in a secure folder. You can also encrypt the data in the tables so if they steal the file, all they'll see is gibberish: 599cd.com/encryption - but you really can't stop them from deleting the file. If you need that kind of security, then you'll have to upgrade the back-end to SQL Server.
![เปิดใจ พี่ญา คนรุม หลังทัวร์ลง หนักสุดในชีวิต!! l [Nickynachat]](http://i.ytimg.com/vi/2-OJZRtclro/mqdefault.jpg)
![POLYCAT - ข้อความรูปยิ้ม [Music Video]](http://i.ytimg.com/vi/lBhIgPGCgbI/mqdefault.jpg)
Hi, I need help please. In runtime mode I am trying to open data ms base B (password protected) from ms data base A. My code fails in this line: Set appAccess = New Access.Application. Thanks.
Hi Richard, one point that's important for new Access users to understand is that Access 32 bit runs fine under Windows 64 bit, but of course not vice versa.
Personally, I run Windows 64 bit, Office 365 64 bit and 32 bit Access. I hope it never becomes necessary to migrate to Access 64 bit.
Yeah, I fought the 64-bit upgrade myself for YEARS. Even Microsoft recommended (at the time) that most users didn't need it. However, since it's now the DEFAULT installation for Office, and most users are getting 64 installed unless they manually change it, I decided it was time. See 599cd.com/32v64bit
Richard: All I need to distribute a module that I wrote in Access 365. It has no database other than the ACCDB that holds the module. How do I point my runtime to the ACCDB that contains the module?
Great but what about the "TRUSTED LOCATION" ????, am I right to believe that trusted locations will be a pain in the neck?
This is great! I thought I have to re-create my database by using another platform. They don't want to get an ms office and I'm almost done with the DB. You saved me a lot of time.
Glad it was helpful!
Desktop application . Split database. How to install on client computer with run time with automatic location getting? Thanks in advance.
And thanks for very good presentation of access. I show many videos of your and Steve Bishop sir. And now I completed my application of accounting with GST for all India in access 2021.
Thanks and obliged❤❤
I've never used runtime because of the need to re-distribute the runtime every time it is changed and the potential need to troubleshoot different client-side issues for different users, which could be pandemonium. A web interface would be much better because the admin could update web code on his end without his users having to do anything other than refreshing their browsers; and all issues would be likely server-side only and easier to manage.
Indeed. However, Access doesn't have a web interface. If you want an Access-only solution, then the Runtime works just fine. I've been recommending it for... Jeez... probably 20+ years now. Since before it was even called the "Access Runtime." It used to be the "Access Developer Extensions" back in Access 95 / 97 / 2000. LOL. Updating the end-users with a new front-end is a piece of cake: 599cd.com/Updater
Awesome video Richard. What about the Windows Installer video?
In access 2021 runtime there is condition that client has which version of Ms office.. The runtime install only that version of runtime. So if your client has Ms office 2016 the runtime will install access 2016. So your application developed in 2021 can not work.
I haven't tested this in a few years, but yes, I believe this is the case.
its good to hear form you, i thought I'd make my database over vb this is a life changer
My pleasure
Hello Richard, Thank you for your wonderful videos. Does One drive have any advantage to use MS Access for multiusers?
NEVER use OneDrive or Google Drive to host an Access database. See 599cd.com/AccessOnline
Images doesn't show up in the Report in Access Runtime. ☹
This was a problem with 2016, but it's been fixed in 365.
Thanks Rick, great info. Just to verify...if I distribute ACCDE file to users who have the full Access program they can't get in and tinker around with my database. They would have to have access to the ACCDB version?
That is correct. They can still get into your tables, just not the design elements (forms, reports, VBA code, etc.)
Thanks so much sir for your help. Following your tutorials I have built a database with forms in MS Access. However, I need to run the Front End on 8 different kiosks running on raspberry Pi which has just LibreOffice. Please is there any way I can do that?
Never tried that before. Sorry.
@@599CD Alright. Thanks for your response.
Sir, How to open password protected database from another database in access runtime environment.
599cd.com/ask
Another great video, thanks Richard 👍👍. I wish I had found your channel years ago. I created and have been developing an application that originally started life in Dbase III Plus 25years ago.
I recently updated my application to 64bit because across our organisation we are migrating to Office 365. I have a few remote users that are still running 32bit Office for other compatibility with other legacy applications. I'm not willing to continue developing different bitness versions of the DB, so these guys are stuck with the last 32bit version that I distributed to them. Can I install the 64bit runtime on their computers with 32bit office?
Also, the DB front end checks that the back end is in the default location before it fully loads. If it isn't then they can browse to the location of the back end and relink to that location. Would this scenario work if I convert the file to an ACCDE file before distribution?
No, you cannot have different "bit-ness" versions of Access (runtime or otherwise) on the same machine.
I cover relinking tables here: 599cd.com/Relink. The extended cut includes code to auto-relink, and yes, it will work in an ACCDE. Time to join. LOL
Richard, thanks very much for this instruction video. I have successfully set up an application to run under the Access runtime setup. The only problem we are having is that we can't get it to print out. This works fine on the full Access developer but not in the runtime version. We get error messages and it shut's down, presumably because the VB part crashes. Is this something that you have come across ? We're happy to join and pay you fees if this is the only way we can get this sorted. All the best from Chester, UK. Mike J
Hi Mike. I've never come across this issue before. Sorry. Give it a Google search and see if anyone else has. Also, my memberships are not for troubleshooting. I don't offer consulting services or fix databases. I teach "how to" do stuff. Good luck.
Is there a Package Solution Wizard (PSW) availabele for Access 2019 (like the one for Access 2007)?
Nope. I know... I used to love the "Package and Deployment" wizard back in Access 95, 97, 2000, etc.
Hi! I just need to distribute a report that has 2 parameters ,do I still need to follow all the steps? Compile, accde file, etc?
Yeah. You can't just distribute one report. If they're going to generate it, they'll need all the tables, queries, forms, etc. to make that report.
If you want to distribute a database and and let the customer run it with runtime on a single desktop. How do you relink the front end to the backend when the user does not have access to the menu's in Access?
You make sure the tables are linked properly before you distribute it, and they're pointing to the same backend location. I recommend a shared drive letter like Z:\Database but a share name will work like \\SERVER\Database
@@599CD Do you have a lesson showing how to do this in code. The people I am helping have no idea how to setup a shared drive and are too far away for me to take the time to drive to them especially since I do not charge them in the first place.
That's more of a networking issue than an Access issue. Sure, I could show you how to relink to the tables in VBA if you enter in what the shared drive is, but if they don't have a network set up already with a shared drive established, that's not something you can easily do from Access.
Hi, I am not able to download off the microsoft website, can you please send me the setup for it!
Sorry, I cannot.
so you give the file location of the database to all your employees .. any of them can just delete it (accidently or intentionally)
Yep. That's a risk you take with Access. People need read/write privileges to the back-end folder. If they know what they're doing, they can open up your tables directly, or even delete the database file altogether. There's not much you can do about it. That's why you need good nightly backups, saved in a secure folder. You can also encrypt the data in the tables so if they steal the file, all they'll see is gibberish: 599cd.com/encryption - but you really can't stop them from deleting the file. If you need that kind of security, then you'll have to upgrade the back-end to SQL Server.
Muchas gracias!, muy buen video, contenido claro, entretenido a pesar de que no es en mi lenguaje nativo, pero entendi todo..Thanks a lot!
Welcome
I am a new Silver member, eligible for the Extended Cuts. How do I find them?
There's a link in each regular video to the extended cut
that was my thumb up, and here is my comment :D ... thank's
Thanks for that!
Please is the windows installation video link available now?
I don't understand.
@@599CD please am referring to the “window installer” in the video (timeline stamp) 12.16 you talked about. please thanks
Will it enable ms access run online/internet ?
See: 599cd.com/SQLOnline
Thanks for this Rick. There is also the click-once version if I remember well
There used to be. Not sure if they still have that available.
Womderful
Thamks
@@599CD Lolololol