I have been programming Access databases for about 15 years and I’ve gotten pretty good at it, thanks to the Tek-Tips Forum. Recently I’ve been laid off and I am out interviewing for a new job – I’m work as an Administrative Assistant. Many companies try to use Excel as a database and in the interview I point out the pitfalls of doing this. So I bring my laptop and give a brief presentation on the virtues of Access in managing data. To entice them into looking at a good example of an Access application I leave them with a nicely developed recipe database which I save on a flash drive. Well over 2,000 recipes, lots of pictures, reports, tons of VBA coded event procedures and lots of macros.
In many cases my interviewer has never even opened Access before and I know that if the default settings in the Trust Center are not changed to enable macros, the database will not operate. So I leave them with a Word document (with print screen directions embedded) that describe how to change the security settings.
I have two questions:
1. Why is Access defaulted to disable all macros from the get-go? After all, macros and VBA coded event procedures are what turns your database into a user friendly application.
2. I need them to select the radio button that states “enable all macros (not recommended; potentially dangerous code can run)”. These are some very menacing words, indeed. Any suggestions on how I can handle this with my prospective employer or client?
Good grief!
In many cases my interviewer has never even opened Access before and I know that if the default settings in the Trust Center are not changed to enable macros, the database will not operate. So I leave them with a Word document (with print screen directions embedded) that describe how to change the security settings.
I have two questions:
1. Why is Access defaulted to disable all macros from the get-go? After all, macros and VBA coded event procedures are what turns your database into a user friendly application.
2. I need them to select the radio button that states “enable all macros (not recommended; potentially dangerous code can run)”. These are some very menacing words, indeed. Any suggestions on how I can handle this with my prospective employer or client?
Good grief!