Quick Queries #29
By Richard Rost
13 months ago
Access Alternatives, Nav Pane, Ad Hoc Relationships
In this Quick Queries tutorial, I will show you how to address common concerns about Microsoft Access including finding alternatives if your company doesn't support it, using Access as a front-end for SQL Server, and securing a split database. You'll gain insights on navigating the navigation pane, managing global vs. ad hoc relationships, and tips for utilizing Access with web-based forms. Learn how to deal with record locks and handling footers within your forms. We'll also touch on effective database management for multiple users, tackling macro recording in Access, and the importance of understanding the limitations and strengths of Access in a corporate setting.
Prerequisites
Links
Recommended Courses
Up Next
Keywords
TechHelp Access, Quick Queries, alternatives to Access, Access VBA, Excel VBA, database front end, SQL Server frontend, ASP for Access, Access PowerApps, Access spaghetti code, Visual Basic criticism, datasheet view restrictions, datasheet in subform, Access navigation pane, Access split database, Access global relationships, ad hoc joins, Access to web converter, Access record locking, form footer issues, Access split user limit, Access macros, custom right-click menus, event countdown form, Access tab controls, Access VBA in Word, Access usability tips, Access development.
Intro In this video, we'll talk about a wide range of Microsoft Access topics based on viewer questions, including alternatives to Access for companies with unsupported apps, working with VBA in Word and Excel, connecting Access to SQL Server, and using tools like PowerApps and ASP for web access. We'll discuss misconceptions about Visual Basic, differences between datasheet view and continuous forms, managing the navigation pane, split database setup and security, global versus ad hoc relationships, integrating online forms, verifying record locks with code, split database user limits, using the macro designer, issues arising from hiding the database, building custom ribbons and right-click menus, setting criteria for event countdown forms, and comparing tabs to subforms in Access.Transcript Welcome to another TechHelp Quick Queries video. This is number 29, brought to you by accesslearningzone.com. I'm your instructor Richard Rost.
What is a Quick Queries video? Well, I make videos and sometimes I get lots of questions that don't necessarily need a whole video on themselves. So that's what I do with the Quick Queries. The video may or may not contain actual questions about queries. We'll see; I'm not sure yet.
Starting off today, here's one I get asked a lot. One of my Gold members Jeffrey wants to know if there are any alternatives to using Microsoft Access because his company doesn't want unsupported apps to be used. If you're using Excel, Word, and Outlook, Access is just another one of the Microsoft Office family. So if your company allows Microsoft Office, there's no reason why they shouldn't allow Access. You can do VBA in Word and Excel too, so it's not like it's a security risk.
I'm of the opinion that nothing is as good as Access when it comes to rapid development of a desktop-based database. And if you've got SQL Server or some other kind of database server in your office or on your network, then Access is a fantastic front end for that, and it gives you all the security that you possibly could need with your data.
As far as connecting to it over the web, you've got things like PowerApps. You've got lots of other tools. Personally, I love using ASP, which is very similar to VBA. It's basically VBScript, an older version, but it's just as easy to use. My whole website is based on ASP. I've got it on my to-do list to do some PowerApps lessons soon. If you are interested in that, let me know; post a comment down below. Likewise, if you've got a good tool that you use that is a good front-end developer for either desktop apps or web-based apps to connect to a database server like SQL Server, let me know about it. Put it down below and I'll check it out.
Next up, moving over to YouTube, Be Jones says back in the day, BASIC was frowned on partly because you could write spaghetti code that worked, but it would take hours to figure out why. One of my favorite memes is the one that says, "My code works. I have no idea why," and "My code doesn't work. I have no idea why." Anyways, I've heard from lots of developers over the years that BASIC isn't a real language. Visual Basic isn't a real language; only real developers use C or C++. Don't listen to any of those people. I've had so many clients run big businesses on code written in VB and there's nothing wrong with it. I mean, how many companies still use old, old languages like Fortran?
You can write spaghetti code with any language really. As far as only having one exit point, that's a good idea because if you have exit functions or exit subs high in your code and then you think you're going to add something to the end of that, you forget that you have an exit point way up the top. That's always a possibility, but again, you could do that with any language. It's just a matter of writing clean code, not necessarily because it's BASIC. Haters will hate. It's like people hating on Access. "Access isn't a real database application." Go get out of here.
Ted Chemist says thanks for this video. Spent the whole day trying to apply restrictions on datasheet view to prevent resizing and deleting columns and all that stuff. I prefer continuous forms myself. I don't like split forms. I don't like datasheet view. But there is one exception, and I've got a video coming out on this soon. I don't mind forms set to datasheet view inside of other forms basically as a subform because then you can give users that Excel experience that they want but you're still using Access. They can resize the rows and columns and stuff and have a little more control over formatting, but you can still control what happens with the events and programming and stuff. Again look for a video coming out on this topic soon.
Jim says if you don't mind asking in your next Quick Queries video, could you provide some tips on managing the All Access Left Margin? I think you mean the navigation pane. Think you talk about this guy versus all access. That's called the navigation pane. I know how you could think it says it's the All Access pane because it looks like that, like I just did a minute ago. But it's just saying all access objects, and yeah, I cover this in detail in my Access course. There are a lot of different options here. Maybe I'll put together a separate TechHelp video on going through all these different things. I generally just leave this on all access objects, and then whatever you're searching for, like everything in my database has to do with customers, has customers in it, and there's all my customers. For orders, I make sure I got order in it.
If you want to see all of one particular type, you can collapse these sections like this so you could see just all of your forms. There are different options up here. You can drop this down and you could see tables and their related views will show you the customer table and everything related to it. I find this to be sometimes a little complicated, so I don't usually use that one, but there are all kinds of different options in here. Maybe a separate whole video on this would be warranted. I know I cover it more in detail in my beginner course. This is called the navigation pane. A properly designed database, once you're done building it, well, you're never really done building it, but I usually hide that. I don't let the navigation pane be something that my users go poke around in. They're going to interface the database with my menu and all the other forms I'm going to create off of that menu. I'm not going to let them poke around on the navigation pane. This is just for you. You're going to hide this when you're done with your database. It can get to be a mess if you're not consistent with your naming. Try to keep everything, even if you got to have like if you got a query that's customers in orders, call it customer order Q. That way, whenever you search for customers or order stuff in that navigation pane, they'll both show up.
Stewart is asking with my open folder video, he says you added a copy of the database the file location and mentioned that the back end should be there if you have one. Does it need to be like this? I'm creating a CRM and would like my team to have x to the filing system, but not necessarily the back end of the database. If you've got a split database solution where your users all have their own front ends and they're pointing to a back end database, they have to have access to that back end folder. Otherwise, they won't be able to use the database.
So that's one of the downsides of just using a split Access solution is that you cannot secure that folder. There are tricks you can play to hide it, and I've got other videos on that. But if you want security, you need to have a like SQL server. If you trust your users and you've got everybody connected to a back end folder where the database is, I suggest putting your filing system folder inside of that folder because I already got access to the database folder on my network. It's the Z drive. Z is a shared folder where I keep my back end Access databases and anything related to it. Files, all that kind of stuff. So yeah, I'd put them together in the same spot. If you've got users that you don't want having access to that stuff, you can always put it in a different secured folder. You could have stuff set up for the accountants in the company versus the salespeople, and everyone can have their own permissions. But you have to do that at the Windows level. You can't do that in Access easily. If you want to learn more, go watch my split database video. I'll put a link to it down below and my simple security video too.
Christian says this must be the first lesson I'm hearing global relationships. I'm not sure what that means. In Access, you've got two kinds of ways to join tables together. There are global or system-level relationships that work throughout the entire database and you have ad hoc joins.
Global relationships are under database tools, relationships, and you add tables into here. You can add the customer table, you can add the order table, and you can join them together based on customer ID. When you do that you can enforce referential integrity and set up cascade deletes and all kinds of stuff, and then this relationship will be through the entire database. However, if you don't want to go that far, I almost never use global relationships, very rarely that I use them. For one thing, if you have multiple back end databases or you're using something like SQL server, those relationships don't matter. But you can set up something called ad hoc relationships between the tables themselves in just a query join.
If you create a query, create query design, you add the customer and add the order table. Now Access created this ad hoc join here. It's a relationship, but it's not a defined global system relationship. It saw that there were two fields called customer ID and it joined them together. I got a whole separate video on this topic coming out, the difference between these two. In the meantime, watch my relationships video if you want to learn more. I got separate videos on cascade updates and cascade deletes and all that stuff. Just search my website, and you'll find all that stuff.
Bia Zanelco wants to know if it's possible to have an online form open and used as a web page, for example in your browser, instead of using Access runtime. It'd be a game changer if Microsoft Access could manage this. I know it's possible to create an SQL server database and blah blah, which would be a hundred times more time than to make with Access for simple projects. Yeah, I get it. It's a lot of work to set up SQL server and define the tables and then connect to it and then build a web page. Is it possible? Yes, and that's exactly how my website works, but it's a lot of work. There are ways that you can use web-based forms like Google Forms or Microsoft's online forms to collect data to get it into your Access database. In fact, I've got a whole video on it. I talk about it in my surveys video where I teach you how to use Google Forms to get data into your Access database. But that's just collecting data. That's not actually working with it and editing it and modifying it and doing that kind of stuff.
I have been kind of playing around with building my own Access to web converter database where basically you take your existing database, like my TechHelp free template database that you're all probably familiar with, and you'll load up my converter utility. It creates a web-based version of your form. I've got to do it; I've got to work in with most of the stuff. You've got to set it up with SQL server first, so the tables have to be stored in SQL server. So you do have to do some setup ahead of time. But my converter can take the entire form and just export it just like this, connect to the table. I've got my own navigation buttons that I build down below. I'm still working on command buttons, so those still have to be worked on. As far as basic form design, it's getting there. I've been slowly working on this one. I have free time over the past year or two. If you're interested in something like this, drop a comment down below, and the more people that are interested, well, maybe the faster I'll finish building this thing. I've been just kind of building it from my own use. Microsoft did used to have something called data access pages, but they dropped support for those years ago. They thought it was too hard to do, I guess, but I've been working on it myself. Let me know if you're interested.
Shloma Spellman, I'm guessing that's right. Glad that you enjoyed my video on record locking. You want to know if there's a way to verify with code if the record is locked when loading a form, so it'd be more user friendly by notifying the end user. Yes, a couple of people have asked me this. You can programmatically try to determine if the record is locked before the user tries to save it. You just basically put some code in the before update. You can use a record set and try to see if you can get access to that record with a record set before trying to save it, and then you can give the user whatever kind of warning you want. I've got a whole separate video coming out on this. A few people have asked me about it, and also in my record locks extended cut I show you how you can implement your own record locking. They'll see "locked" up here, and it will actually tell them if the record is locked because you're storing the record locking in your own table. That's another way you can do it. There are lots of ways you can do this stuff, folks. One of the reasons I love Access.There's like three ways you could do everything. All right, next up we have Michelle and yes, I can tell that's a Michelle, that's an easy one.
Thanks for the video. I'm having an issue where I do have a footer that I can see in the design view and I added some calculation under the footer. You mean in the footer. But when you go to the form view, it does not appear in the form. Is there a setting that I'm missing?
First of all, make sure that you're in the form footer and not the page footer. A lot of people make that mistake. The page footer only shows up when you print it, and of course, we don't print forms; we print reports.
Second, make sure that you've got the visible property on. Make sure that your foreground and background colors aren't white. I've seen that happen before. There are a million things it could be.
This is why I like it when people post questions in the forums on my website because you can include some screenshots, and I can see what's going on. This isn't enough information for me to tell what's wrong without knowing a lot more. Hope that helps. Check those few things.
Next up, Math G is asking if there's a user limit on a split database. He wants to do this for a team of around ten users. Ten users should not be a problem. I have set up databases for clients with 20, 30, sometimes 50 users at the same time. It has more to do with the quality of your network than it does with the actual number of users and how much traffic they're using.
First of all, you want to make sure everyone is wired. Don't try running Access split databases over a wireless network. I've had lots of problems with those. Just the nature of wireless networking, you don't have a 100% consistent connection all the time. Networks drop here and there. With a wired connection, you should have far fewer problems.
If most of your users are just looking up data and not doing a lot of data entry, you can have more users on the network. It's when record locks start getting involved and lots and lots of people are editing stuff that you run into conflicts. Ten users should not be a problem if you've got a modern network with no problems. Twenty users is even no problem. If you go beyond 20 users, that's when you want to start thinking about a backend server solution like SQL Server. But for ten users, you should be just fine.
To answer your question though, I believe if memory serves, the theoretical limit is 255 concurrent users if memory serves. Let me Google it real quick here, hang on. Yes, the Google machine confirms that: 255, but realistically, 20 users is pushing it, 50 users if it's really light usage. So that's my experience, 10 no problem.
Hanju wants to know, can you do those steps in macro recording? Access doesn't have a macro recorder like Word and Excel do where you can start recording and then do a bunch of things, then stop recording, and then it'll replay that. Access has a macro designer where you can pick actions from a list. I've got a whole separate video on it. Start with this video; it'll give you the basics of what macros are.
Hey Hoov's writes: I have another strange issue. I hope you might try some light on. My assistant inputs information on a ticket form each morning. Since I hid the database, the information she inputs on the form does not register on the table. However, when I input the information at a later time, the information registers in the table. This has only been happening since I hid the database.
I'm going to guess that you may have inadvertently created two different database files, and she's actually typing in information and it's saving it in a different database file. So double-check that, make sure you know where your tables are linked to. Also, make sure it's not a duplicate table. I've had that situation before too, where people have created a backup table inside the database like customer 2 or whatever, and they're actually saving the data there, and someone else is linked to a different table. So it's either a different database file or a different table.
If she's typing information in and she can move off the record and move back to it and see that the record is there, there's no reason you shouldn't be able to see it. So it's probably one of those two things. That's my guess.
Another question from Hey Hoov's: He hid his database with the steps I showed in this video, and you lose the ability to right-click. Yeah, that will disable the right-click menu. It also disables all the ribbon buttons. You can't solely use Control-C, Control-V, Control-X to copy, cut, and paste. There's not much you could do about that except create your own buttons or you can create your own right-click menus.
My dog's barking, hold on. See, I try to be nice when I'm home alone with the dogs and I leave my office door open so they can come and visit me, but then if we get a delivery, the UPS guy shows up or whatever, then my dog goes crazy. If this had been an official course, I probably would have re-recorded that, but for a quick queries video, you guys get to listen to my dog barking.
Anyways, no, anytime you go and hide the Access framework, you're turning off a lot of functions too. So you have to either build those things yourself or reinstate the default Access ones. I do cover all of that in my developer lessons. In Developer 44, I show how to build custom ribbons so you can put your own stuff up here. And in Developer 45, I show you how to make custom right-click menus so you can put your own stuff on here as well.
Sorry, those are your only two options. You can either restore the Access default stuff or build your own, or you could make little buttons on the form too if you want to use copy, cut, and paste buttons. Sometimes I put those right on my forms if there's fields that I copy a lot. I'll throw a copy button right next to it, and you can just click on it, and it'll copy that text. I got another whole separate video on how to do that, like in this video. Copy the address and puts the address down here, hit the button to copy it to the clipboard. You can do stuff like that too if you want.
Izick asks about my event countdown form: how to get only upcoming events to show up and not show the ones that are past. Yeah, I use this myself. I have this up in my office. My now wife and I, I hate saying fiancee, so we finally got married. But anyways, we use this for upcoming trips or like her mom's coming to visit next week, so it's on my little server in the corner there. But I like seeing the negative number up there because then I know I gotta go and delete it, but that's just a matter of use a query and make it so that that number has to be greater than or equal to zero or it doesn't display.
In fact, here's mine and my database: Lauren's mom's coming; she'll be here in five days. I'm heading up to Orlando in 16 days. We're going to Seattle for the Microsoft MVP conference and for Access Day in 27 days, and yes, I've got the Spain eclipse in 2026 on here. Ever since I saw the last eclipse in Dallas, I'm hooked. So I'm going to go to this one too. I'll figure it out. Got two years to worry about it.
But yeah, this events form is based on, if memory serves, an event query. It's been a while since I built this. Let me see. Open her up, and yes, it's events Q. So let's open up events Q. Yep, and then right here, days left, you just put a criteria right there that says greater than or equal to zero. That's it. I'm not going to do it in mine, though, but I like it like that. So nope.
And you can learn more about Access query criteria in this video.
Robert says tabs can be a pain. I wonder how many bugs have been improved in the four years since this video, how many have been improved and how many have been added. As with all software developers, the Access team fixes, and the Access team takes away.
I've never liked tab controls, as I said in that video from four years ago. Just when they first came out, they were riddled with bugs, and I know they've gotten better since then, and you can do some stuff with them, but I just don't like them.
I like using a subform, and I make my own little tabs, either buttons or labels, and then I just swap the subform out. It works so much better for me. That's just my personal preference. I've always hated tabs, but you might like them, give them try. Let me know what you think.
I know this is based on a Word video, my batch convert video, but I want to just include this in here because Access users, you might want to go watch this batch convert video even though it's about Word because there's a good amount of VBA in it, and the VBA is very similar between Access, Excel, Word, and PowerPoint. This is a really good lesson for learning some VBA, even though it has to do with Word. It's still cool stuff, and you can do stuff like this from Access too.
But Nimish, to answer your question, yes. I miss WordPerfect. I used to love WordPerfect for DOS 6. I think I had 6.0 or 6.1 like you did. It was the white text on a blue screen. Remember that? I remember like it was yesterday. I loved this. So yeah, I do miss it. Things have gotten better, but back in the day, this was the jam.
Anyhow, that's gonna do it for today folks. Enjoy the rest of your Friday, enjoy your weekend. Hope you learned something today. Live long and prosper. I'll see you next time.
TOPICS:
Alternatives to Microsoft Access
VBA in Word and Excel
Access with SQL Server
PowerApps and ASP for web access
Visual Basic misconceptions
Datasheet view vs. continuous forms
Navigation pane management
Split database and backend folder access
Global vs. ad hoc relationships
Online forms and Access integration
Record locking verification with code
Split database user limits
Access macro designer
Database hiding and data entry issues
Custom ribbons and right-click menus
Event countdown form criteria
Tabs vs. subforms in Access
COMMERCIAL:
In today's Quick Queries video, we'll tackle a variety of questions on Microsoft Access, covering everything from alternative solutions to Access for unsupported apps, to coding in VBA and managing navigation panes. We'll also discuss how Access compares to other languages like BASIC, address dealing with user limits on split databases, and look at whether you can verify record locks with code. Plus, learn about using forms as web pages and managing event countdowns efficiently. You'll find the complete video on my YouTube channel and on my website at the link shown. Live long and prosper my friends.Quiz Q1. What is the main purpose of the Quick Queries videos?
A. To provide full-length tutorials on Microsoft Access
B. To answer questions that don't require a full, dedicated video
C. To focus solely on query-related questions
D. To provide expert interviews with Access developers
Q2. According to Richard Rost, why should companies that use Microsoft Office also consider using Microsoft Access?
A. Access is the only database software compatible with Excel and Word
B. Access poses a security risk similar to Excel and Word
C. Access is part of Microsoft Office, so it should be safe to use if other Office products are allowed
D. Access is the only software available from Microsoft for data management
Q3. Which language does Richard Rost mention as being frowned upon by some despite its capabilities?
A. Python
B. C++
C. BASIC
D. Java
Q4. What does Richard Rost think about the use of VBA with Access compared to 'real' programming languages?
A. VBA is not suitable for any serious application development
B. Only C and C++ are suitable for professional programming
C. VBA can be used effectively for running big businesses despite criticism
D. VBA is mostly for educational purposes
Q5. What does Richard Rost recommend for applying restrictions in a datasheet view?
A. Only use split forms
B. Use continuous forms for better control
C. Rely solely on Excel for such requirements
D. Avoid datasheet view altogether for security reasons
Q6. What does Richard Rost suggest for users who access the backend of a split Access database?
A. Each user should have direct access to the backend database folder
B. Security can only be managed through Access settings
C. Use SQL Server for better security if folder access is an issue
D. Prevent any user from accessing the backend to ensure security
Q7. What is the function of global relationships in Access, according to Richard Rost?
A. They are used for temporary data joins only
B. They create relationships at a system level, impacting the whole database
C. They are outdated and should not be used
D. They are mainly used in web-based applications
Q8. What is a limitation of using macros in Access compared to Word or Excel?
A. Macros in Access are fully automated and cannot be modified
B. Access does not have a macro recorder like Word or Excel
C. Access can only execute macros if connected to SQL Server
D. Macros can only perform calculations in Access
Q9. According to Richard Rost, what is critical for a split database to function effectively with multiple users?
A. A powerful server dedicated exclusively to Access
B. Wireless connections for all users to maintain flexibility
C. A strong and stable wired network connection
D. External hard drives connected to each user's computer
Q10. Why might hiding the Access framework cause limitations for users?
A. It disables the program entirely
B. It removes all menu and right-click options
C. It forces users to write VBA code for every operation
D. It makes the database inaccessible
Answers: 1-B; 2-C; 3-C; 4-C; 5-B; 6-C; 7-B; 8-B; 9-C; 10-B
DISCLAIMER: Quiz questions are AI generated. If you find any that are wrong, don't make sense, or aren't related to the video topic at hand, then please post a comment and let me know. Thanks.Summary In today's Quick Queries video from Access Learning Zone, I'm addressing several common questions that don't require a full video themselves. Quick Queries is a segment where I address various topics about Microsoft Access and occasionally other related queries.
Let's start with a frequent question from one of our Gold members, Jeffrey. He inquired about alternatives to Microsoft Access since his company is cautious about using unsupported applications. Access is a part of the Microsoft Office suite, just like Excel and Word, and should be equally acceptable if your organization endorses Office applications. It uses VBA in a similar fashion to Word and Excel, thus posing no additional security risks. When you need to rapidly develop a desktop database application, Access is unmatched. If your workplace employs SQL Server or another database server, Access serves as an excellent frontend, ensuring robust data security. For web connectivity, PowerApps and ASP offer viable solutions, the latter being user-friendly and akin to VBScript.
Switching to YouTube, Be Jones reflects on how BASIC was often criticized due to its potential for forming spaghetti code, which could be hard to debug. Despite such criticisms, I see nothing wrong with BASIC or Visual Basic. I've seen many large companies successfully run operations on VB code, emphasizing that it's all about writing clean code, not the language itself.
A comment from Ted Chemist mentions spending much of the day figuring out how to restrict datasheet view in Access. Personally, I prefer continuous forms over datasheet or split forms, but using datasheet view as a subform within another form can provide users with a familiar Excel-like experience while maintaining control over events and functionality within Access.
Jim is curious about managing the All Access Left Margin, known as the navigation pane. I cover it extensively in my Access course. This pane helps organize forms, tables, and other objects, allowing easy access and management. Keeping it organized and consistent is crucial, although it's not typically visible to end users in a well-designed database.
Another question from Stewart about database architecture—having access to back end files is essential for a split database setup. If security is a concern, then more robust solutions like SQL Server are advisable. However, for simplicity, putting related files in the same directory can work if your users are trustworthy.
Christian raises the concept of global relationships versus ad hoc joins. Global relationships are applicable throughout the database, while ad hoc joins are specific to queries. Both have their uses depending on database setup and requirements.
Bia Zanelco wonders about using Access forms online instead of the Access runtime. While converting Access forms for use on the web is complex, integrating tools like Google Forms can facilitate data collection for Access. I've been working on an Access to web converter that simplifies this process, contingent on using SQL Server for data storage.
Shloma Spellman asks about detecting record locks programmatically. Before an update attempt, you can check if a record is locked and alert the user accordingly. I'll be releasing a video on this, and also touch upon it in my extended cut about record locks.
Michelle wants to know why her form footer doesn't display as expected. Ensure it's set as a form footer, not a page footer, and confirm properties like visibility and color settings are correct.
Math G's inquiry is about the number of users a split database can support. Typically, ten users shouldn't be a problem on a reliable wired network. The theoretical user limit is higher, but practical constraints often advise using a more robust backend like SQL Server for larger groups.
Hanju is interested in whether Access supports macro recording like Word and Excel. While Access doesn't provide a macro recorder, it does offer a macro designer for executing actions, which I explain in my videos.
Hey Hoov's faces issues with consistent database updates, possibly due to duplicate tables or mislinked databases. Ensure all users update the correct database location and table to maintain data integrity.
Lastly, some questions about features such as tab controls and VBA elements suggest further exploration into best practices for form design and the integration of VBA across Office applications.
For those curious about batch conversion in Word, despite being a Word topic, it can teach valuable VBA skills applicable to Access.
I hope this session has been informative. You can find a complete video tutorial with step-by-step instructions for everything discussed here on my website at the link below. Live long and prosper, my friends.Topic List Alternatives to Microsoft Access
VBA in Word and Excel
Access with SQL Server
PowerApps and ASP for web access
Visual Basic misconceptions
Datasheet view vs. continuous forms
Navigation pane management
Split database and backend folder access
Global vs. ad hoc relationships
Online forms and Access integration
Record locking verification with code
Split database user limits
Access macro designer
Database hiding and data entry issues
Custom ribbons and right-click menus
Event countdown form criteria
Tabs vs. subforms in Access |
