VBA to open form when opening Database

[Glenley]

I know this can be set in the current database options but is there a way to set a form to open when opening a database with VBA. I'm trying to prevent people in the office from being able to change it in their settings without disabling the ribbon. TIA

[Welshgasman]

Use a macro called autoexec and open the form in that.
However, db should be an accde? Then I think that option might not be available. You would need to check. Plus disable shift bypass.

[Glenley]

Yes, I always distribute the db files as accde and thus far, I don't think anyone in the office knows about shift bypass but I don't like depending on that for db security. We're starting to get more people in the company and I'm trying to compartmentalize the different departments without having to customize every individual db file

[Glenley]

I went with the AutoExec macro method. I actually forgot about that option

[Micron]

You can disable shift bypass? I realize if you know what you're doing, you can over-ride it, but I'd never reveal how to do that in a forum. I used to have a label on a form that was red if enabled, black if not, in case I wanted to check if I left it off in an updated db. Enabling it doesn't get a nosy user very far in an accde anyway? I would have thought that accde file would not allow the changing of the opening form, but if it does, why bother having it when you can load it via code - which the user cannot change?

[Glenley]

I was shown a method to disable shift bypass in a security seminar I took when I first started learning VBA. I used the code in the project db we built for the class but have never used it in my office db. Being a small company, I haven't really felt the need to get that extreme about security.

[Micron]

I haven't really felt the need to get that extreme about security.

Then the horse has not ever left the barn - yet.

[Glenley]

Like I say, we're a small company. It's not really malicious intent that I'm worried about, it's people messing around in places they're not supposed to be and clicking things they shouldn't be clicking which has been a problem in the past. My boss is being the biggest violator. A huge part of the time I've spent building our db has been figuring out ways to prevent that

[Welshgasman]

I know where you are coming from.
I also worked in a smal company and luckily for me, mine were only used by managers or just myself.
Still made accde though, evern when for myself. In fact if I open one now here at home, it comes up with a warning 'this is not the accde'
That was implemented when I created a DB for lloyds bank, and some people would copy the wrong file. At that time, I was not aware of auto FE updating.

[Glenley]

Auto FE updating? I'd love to know more about that. We are not operating on a local network. Our BE tables are hosted on SharePoint if that matters at all

[Welshgasman]

Well, I would have thought your pcs would be on a local network?

[Welshgasman]

I used Bob Larsen's FE updater.
Gicu here also has his own.

Google https://www.google.com/search?q=acce...&ie=UTF-8#ip=1

https://www.access-programmers.co.uk...-users.305393/

[Welshgasman]

Here is the Bob Larsen one.
Gicu (Vlad's) as well.

https://www.access-programmers.co.uk...tility.320072/

Others just use a batch file that copies the master fe each time the user fe is opened, normally by a shortcut to a batch/cmd file.

[Glenley]

Thank you very much. I'll check out these links. Yes, we're a small business but half of our organization is spread throughout the US doing sales. The best solution we could find to have cloud server based tables without the costs of SQL Server was SharePoint. We'll eventually outgrow SP but it has worked great so far. As of right now, we're dealing with less than 10k records