Search results

Surprise, surprise... :rolleyes: --Not-Shocked Mac

Two things: (1) You might try putting your checking code into the individual BeforeUpdate events of the respective controls rather than the form. Just a thought. (2) Add an undo into your code. See this thread, among others (search the forum on "cancel and save and message"). --Grasping Mac

You can set warnings to off just before your cancel statement and set them back to on just after. Check Access help for "setwarning" Caveat Emptor: Always be careful to turn your warnings back on! --Latin Mac

Glad you have it working--just be very, VERY careful with cascading deletes to make sure that you keep them within very specific limits. On your setup, for example, you wouldn't want to tell Access to delete a student and end up deleteing all the courses that they're registered for! That's why...

I'm sure there's a better, simpler, more elegant answer, but until it comes along, you could add code to the button's OnClick event that will delete the related records. A couple questions for you: Are you using, as I'm guessing you are, a link table between the students and courses tables...

Maybe so, but I bet you kick his a$$ at normalizing tables... :D "Bridges? We don' need no steenkin' bridges..." --Number-One-Fan Mac

My current sig says it all... Pat's answer is, as usual, concise and on-target. If you need a hand with the "how" of getting the info from/to the right places after you implement Pat's corrections, just shout out. --Pat's-Groupie Mac

Oh, sweet clarity... Not sure I do know for certain what you're on about, but let's see if we can find out. Number 1 sounds like you have a combo box that gets its info (rowsource) from a table other than the table ("table A") which is the datasource for the form itself, yes? And you store...

Looks like I have to change my sig to "WWRD?". --Apostle Mac

Any event could make it happen, but since it occurs when you click inthe subform, yep, yer probably right. Another place to check might be the .OnGetFocus of the subform. What puzzles me a bit is how this code found its way into your forms to begin with. Did you create these forms & subs from...

Then, as usual, Rich is right. No surprise there. How familiar are you with VBA and event properties? --Unsurprised Mac

It may be helpful to read this Bang vs. Dot article. --Suggestive Mac

Rich - if it's a subform, could the first click, wherever it lands, be activating the subform, and since control "A" has the 0 tabbing index, it's getting focus? Stefan, try clicking on control "B" and see what happens. Just a random thought... Anyway, what Rich is referring to is a piece of...

Progress...

Neil -- Any recommendations? --Intrigued Mac

You shouldn't be trying to have your command button CREATE a form, at least not at this stage. Design the form as you did the first one and have the command button open it. --Quicky Mac

Umm... figure it out? Seriously, what are you asking? Are you looking for opinions on the best way to proceed, or are you asking how to set up a command button to open a subform, or are you hoping someone will set this up for you? What's the specific question? Yes, you can easily have a...

Are you sure you gave the sorting/grouping options of the report design a thorough look? ;) From Access Help: Always check help first and search these archives second. --Enabling Mac

Happy to help. The "indirect route" question was simply that I don't understand why you're going through the trouble of putting extra fields in your tables to run searches (queries) to find information, when you could just base the queries on the relevant fields directly. Looking back at your...

Whoops! Sorry about that. Hopefully you can open this one... Responding to your responses... Seems like you're building a ladder to reach the top of a staircase... What does using this indirect route allow you to accomplish that you couldn't by just building your query on the actual values...