Upgrade your account to a Community Supporter account and remove most of the site ads.
Rocket your D&D 5E and Level Up: Advanced 5E games into space! Alpha Star Magazine Is Launching... Right Now!

Reply to thread

Message: <blockquote data-quote="Andre" data-source="post: 2314070" data-attributes="member: 25930">Did you, by chance, import the switchboard and its underlying table from the earlier file? If so, I would suggest recreating it from scratch. Switchboard forms can be a bit flaky and importing one into a different file might cause problems like this. Alternately, check to see if the forms are opening to a new record - if so, you can change this in the switchboard properties. Another possibility is a problem with the record source of the form. Open it both ways and check the record source to verify that it's the same. BTW - When you open a form with the switchboard, try going to design view, then back to form view. If your data suddenly appears, then it's probably a problem in the switchboard properties.  Consider hiding the database window on startup, but only if you leave a method for bringing it back (so you can make changes). IIRC, <F6> will bring it up. Alternately, I tie a small bit of code to a logo or other object, so if I double-click it, the database window appears.Later you'll want to create custom menu and toolbars for the application. Absolutely necessary if you want to "idiot-proof" the database. Just always save a copy of the file before making significant changes - helps you avoid problems such as the macro you mentioned above. I understand where you're going with this, but it will require some vba programming to pull it off. A simpler technique is to tie the main form to a combo box. The user can start typing in the combo box, then hit [Enter] when the correct name is displayed. Not much extra effort for the user, but much easier for you if you're not comfortable with vba programming in Access. Note: you'll need to add some error-trapping at some point, as I've seen people start typing, then erase what they've entered, then try to click something else on the form. This prompts an error message, as the combo box doesn't like the null entry. Irritating...I'm not a big fan of form/subform for entry, as I don't think it's always intuitive for the casual user. If you're willing to dig into the code, I have a form I modified from someone else that allows me to link contacts with groups (think distribution groups in Outlook). You could easily adapt the concept to Patrons and Performances. Basically, the form would display two list boxes, one for patrons, one for performances. The user highlights one or more names, clicks the add button, and the selections are added. An almost identical form would allow the user to select multiple performances and add those to one patron. Very user-friendly (with proper error-trapping, of course  <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink    ;)"  data-smilie="2"data-shortname=";)" /> ). A control button, with the Apply Filter action tied to it. Create a query for the parameters you want, then apply that query as the filter. I used this idea for my 3.x database of monsters, spells, items, and so forth. Same as above, except the button has an Open Form event tied to it. It's usually good design to minimize the current form before opening the new one, then restore the old form when the new one closes, but that's not strictly necessary.If you want to zip the file and send it (w/o any sensitive data), I'll be happy to take a look and make more detailed suggestions. I'm at <a href="mailto:sirwhiskers@att.net">sirwhiskers@att.net</a>.</blockquote>

Verification