Search results for query: *

THe following will simulate a page down/up response. You can add the pertinent line of code directly to a click event, or create a module. But I am not sure this will get you were you want to go. Overall I am not sure why you are in the straights you are. Why would you need 11 forms/subforms...

Copy and Paste sounds like the easiest route. Cheers, Bill

I believe Access 2002 allows considerably more latitude with forms in continuous view. Alternatively you can create a table to be designated as a temporary table. USe it to append your category data and then you can bind the form's controls to the temp table. Cheers, Bill

Create a 2nd query based on what you already have and preface the SQL statement with the TOP predicate as in: SELECT TOP 3 ......... Cheers, Bill

You have an unbound control so you can use a VBA embedded SQL statement run from an appropriate event: DoCmd.RunSQL "INSERT INTO tblYourTableName (YourFieldName) VALUES (Forms!frmYourFormName!ctlYourControlName);" Cheers, Bill

A Google search under database models will keep you in reading material for a while. Cheers, Bill

Describing where you want to go with the "Tab" is helpful and I think a combo box will fit your requirements. 1) You can play with its Special Effect properties to change the appearance. 2) Add the following to its OnEnter or OnClick event: Me.YourComboBoxName.Dropdown to get a...

Mike, Tables are still 2-dimensional (i.e. flat). Cheers, Bill

THere must be a catch here somewhere. If the db's are identical, why draw data from both? Puzzled.

What is it you want to show? Any reason to use combo boxes rather than text boxes? Are the combo boxes bound? Are the combo boxes on the subform? More info will be helpful. Cheers, Bill

Nick, You haven't provided enough info for a definitive answer, so here are some possibilities. 1) The query is more complex than you think; 2) You have aggregate functions in the query; 3) Join tyoes preclude an updateable recordset; 4) The query is based (in entirety or in part) on...

Insert the following in code before running the query: Docmd.SetWarnings false After running the query, restore the warnings: Docmd.SetWarnings True Cheers, Bill

Look at the Refresh method on an appropriate event (in your case perhaps the subform's on current event). Cheers, Bill

Ryan, If you decide to stay with the previously discussed many-to-many table structure, then Josh's suggestion on the form-sub form design is where you need to go. However I am going to toss out another suggestion for table structure, that may be easier to maintain and under the circumstances...

Several versions of Access have a query wizard that will guide you through creating a query for unmatched records. But basically you will create a SELECT query with a left join between tables (all records from tblPeople and those records from tblSick where the joined fields are equal). Further...

UPDATE Table SET Table.YourField = "999" WHERE (((Table.YourField) Is Null)); Cheers, Bill

If I have understood your question correctly, create a SELECT query joining table1 and table2 (include the fields containing the client name) and use this query as the subform's recordsource. Cheers, Bill

In addition to Raymondo's suggestion, you can handle it from the query that provides the report's recordset. Open the query in design view, select the key field (the one that will distinguish the record in both the form and report) and then set its critieria to: Forms!YourFormName!ControlName...

In addition to Raymondo's suggestion, you can handle it from the query that provides the report's recordset. Open the query in design view, select the key field (the one that will distinguish the record in both the form and report) and then set its critieria to: Forms!YourFormName!ControlName...

In addition to Raymondo's suggestion, you can handle it from the query that provides the report's recordset. Open the query in design view, select the key field (the one that will distinguish the record in both the form and report) and then set its critieria to: Forms!YourFormName!ControlName...