Search results

I thought subdatasheets only load when a table is opened directly?

You may run into issues if you ever export this data to a spreadsheet and plan to work with it there. In my experience, the Format function results in numbers formatted as text. Therefore, you won't be able to perform any calculations on the data until you use the =VALUE function to convert...

End users should never see the tables... As a developer, I have found scenarios where turning them on to inspect data relationships between tables was a huge help. Pretty sure that's why they're there. Otherwise it really doesn't matter once your app is up and running.

I don't use union queries (or at least I haven't had a need for them) but my Select query results are fine. I don't see lookup fields in tables as having anything to do with the queries and joins I use throughout. They are not mutually exclusive.

Oops, forgot that important part. Edited.

Here's mine, using a tweaked version of CJ's method. Subform footer has an unbound invisible text box named txtPK On Current event of subform contains the following: Me.txtPK = Nz(Me.[yourprimarykeyID], 0) Conditional formatting is applied per attachment Field will highlight as you move...

I like the idea that you can create an HTML email. EMailDatabaseObject works but is plain text only. Also, it has a bad habit of leaving a dead Outlook instance running that you have to kill with Task Manager. The Outlook email window also takes over like a dialog form while it is open...

CJ, do you mean Work Folders? Work Folders is how it's being done now. You run your files from your hard disk, and there is a background process that is basically online backup to the domain server. That way, there are no performance issues. If you move to a different computer and log in for...

Our IT department does disable installation of software except by Admins. So, you can try this. Create a new macro and in the blank macro designer, paste this: <?xml version="1.0" encoding="UTF-16" standalone="no"?> <UserInterfaceMacros...

Makes sense. My DB exists in a production environment where data is entered and reports are printed out. Therefore all functionality needs to be baked into the forms and I try to make it as bulletproof as I can...it's a lot of work, but it's rewarding when it all works. I admit I have pulled a...

Can you tell me what this would net me? Maybe I wasn't clear, but I already hide everything and lock down the DB. At first glance it looks like you let users access the navigation pane. Mine is completely unavailable and I intend to keep it that way...

Ok, I shift bypass my .accdb to do development work. When I do, it also bypasses startup restrictions on hiding the ribbon, nav pane, and shortcut menus. So, the nav pane is already showing when I bypass. Still, my users aren't doing that on their .accde as I disabled the bypass. :)

I just opened my database and hit F11, nothing happens. Nav pane still hidden. What am I missing? Tried all the other F keys - just realized F12 will perform the Office "Save As" for the form. None of the others do anything, but I should probably see about disabling that. It might not matter as...

Definitely get your forms developed so you can get a good workflow going with them. Design and use the forms from the perspective of someone else using them. Access isn't much better than Excel if just using tables. Good luck!

I didn't, but I usually just hide the navigation pane, ribbon, and everything so nothing is visible at all. No need to hide objects individually in my case :). I don't have users making queries though, at this point.

You would use a query to reopen a case for someone on request? Seems a bit cumbersome...that is one use-case.

In most/all cases, yes. Users would use forms. But I'm talking from an admin's perspective. Users won't encounter any issues while using the DB if you designed it properly (as you would, anyway). They won't have access to the tables. But it sure makes it easier for an admin to troubleshoot...

As long as you know what is going on, I do not think it's a big deal. All it is is a table-level lookup. So as an admin, I can change a value if needed and choose from real names instead of having to refer to a lookup table to find the right ID.

I use that as the control source for a text box on my report and for a field in datasheet view on a form. What I posted is actually a copy and paste from my DB, with changes to your specific names.

Just wanted to say that 8:00 AM - 9:15 PM is a long day in Access!