Search results

And my education continues... (Could someone please remind me to shut up?)

Rich, Is it possible that this is something that has varied between versions of Access? I tested my beliefs in A2002, and I'm pretty sure that's what I've got happening. Of course, I'm not using code to change the focus, just the mouse. Or maybe we're saying the same thing in different...

Wayne, As I understand them [please educate me if I'm wrong] Pop-up forms are always on top but will surrender focus to another form. Modal forms will not surrender focus with a mouse click on the other form. If both properties are set to yes, you get a dialog box that will allow you to do...

On another re-read of your original post, this occurs to me... your combobox, is bound to a query, which I suppose returns the results you want to populate the other form controls... Then perhaps: =Forms!FaceSheet!DoctorID.column(0) will return what you want if DoctorID is the 1st column in...

First you said: "Table and Form One are titled "Face Sheet" and has fields for DoctorID, Doctor Name, Doctor Address, and Doctor Phone." Now you say: "The Face Sheet table stores only the Doctor ID " The question I have is: If the Face Sheet table stores only the Doctor ID, and Doctor List...

quote from Access2002 Help: To fix [or set] a missing reference, open a module in Design view, and click References on the Tools menu. Then clear the check box next to any missing references and set the references you want.

First: Is there a good reason to store the same info in 2 different tables? Ordinarily that only creates problems. Secondly: if you want this for printing purposes, you would probably be better off using a report rather than a form.

depends on your needs If EmpID has only 1 or 2 cell phones at any given time, the tables should likely be combined If EmpID is the salesman selling many phones, probably best as is

No problem setting the relationship on my machine

isn't that pop-up? if the form is modal, it would be impossible to click the other form to set focus [as I understand it]

Are you sure that's what you really want? I tend to think you'd be better off by adding frmOrderData as a subform on frmClientData. If the relationships are right, then your users could see the faulty order, and make the corrections easily.

Is it necessary for some other reason that you should have a custom form for the input of query parameters? If not, just prompt for the parameters in the criteria of your queries, and let Access generate the input prompt/form for you. Probably less code to write as well. Just a quick thought...

Calvin, Sorry I neglected to get back to you (I've got some lame excuse about lack of time) but I did want to let you know that I was able to use the bit of code you offered, and I did get the On Not In List event to fire it. Again, Many Thanks!

Right-Click on the Macro name, select Save As, in the combobox select Module.

Pat Hartman is right to say: But, if you're in a continuous form, it is simple enough to click on the record selector [the vertical bar to the left of the record] and then hit the Delete key. The user is then prompted to confirm their choice. No query, No code. HTH

No primary key?

That's tough to do, Jack. There's only 1 field being appended. (other fields are only used for criteria) It is a lookup value from a table of names. What displays is the list of names, but the actual value appended is the primary key from that lookup table. It is being appended to the lookup...

I've designed an append query that returns the correct results in preview, but raises key violation errors when run. I've searched all over for help info to correct this, but have found little to guide me. Any ideas?

You know, maybe it won't matter. If I've spoken out of turn, I apologize. :o As a relative newbie, I often use the wizards to accomplish my goals in Access. Perhaps the FindDuplicates will get you there without the table splitting. Also, there is a wizard for splitting the tables, should you...

Glad to hear I wasn't the only one that didn't quite get that!