Search results

Do you have records in the tables? If not, it is probably because the data types might not be same (if using autonumber pk's ensure your fk's are long). If so, you can only probably create it one way because records exist in one table and not the other (the way you want it). For instance ...

I think that was one of the issues, that there are no nulls in the dataset - a record is there or not. I couldn't use groups with a LEFT JOIN because if there was data in one group (say for state A) that group wouldn't show for a different state (B) where there were no people in that group...

You bet. Good luck. -dK

Other than turning on an 'add to list' in the combo box properties, you have to ensure that the country code is updated along with the added city. If I don't have a seperate interface or doing control level access rights, I usually refer to this link for adding to a list. I like their...

Okay. I see. DLookups are not the way to go, but I mentioned it to demonstrate how far off-based I was thinking. Grouping on the profession may not work because you want the professions the be displayed even if the dataset does not contain any. I don't know of a way to force that but perhaps...

Yes. What you have is a combo box that is set to the primary key (instead of a foreign key) of a table so this will throw an error because it is an autonumber on a new record. The last attachment I posted works because it is all set up nice and neat on a table-bound form where you are only...

Will the user's be adding cities to the country's off of this form? Or will they merely be selecting the country/city? -dK

I see what you are saying but having difficulty in understanding because I don't understand the structure. In addition, I am looking for the most efficient implementation that fits your needs. So when you run this report, is it for an individual 'thing'? That is, let's say it is for a...

Here is correct attachment. -dK

Here ya go. This is the quick fix - the form is bound to the table, but that is not how you have it specified in your initial cut. I am not entirely satisfied with this because we are duplicating a field. In the databases I have created - I have avoided this issue because of the way I set up the...

Yah .. it is doing something weird - it has been awhile since I actually have set one of these up in this particular fashion. I know the quick fix (bound the table to the form and add a field), but I am sure I am overlooking something to base the form on the initial query you had specified. I...

Opps .. I didn't finish the job - forgot to set the forms source correctly. -dK

I didn't put the country code in the University table because I did not see a need. You can reference the country code utilizing the relations through the city table. However, if this just has to happen then add the field back to the table and in the AfterUpdate event of the country combo box...

Ah. I hate it when that happens. Awesome it is working for you now and thanks for posting back. Good luck in your projects! -dK

I normalized a couple of things and cascaded them to what I think you are going for. Check the relationships, combo box data sources and the code behind the City combo box to see what I did. HTH, -dK

If I get this right, your report runs and you want ... Accountants Acct Name1 Acct Name2 Doctors Dr Name1 Lawyers Lwyr Name1 Lwyr Name2 If this is correct, why not just use the grouping levels on the report and not worry about an If to present these for you? -dK

The link I gave you uses the properties of the forms .Filter property. Once you have the query constructed, it will populate the form and then it will be filtered according to the form control inputs. -dK

Try that in the AfterUpdate event of the unbound text control (Text0). -dK

Hoopty! Just checking in .. what was the final solution? -dK

Check to make sure it is a label control you put on the form and not a text control. -dK