Search results

Have you seen the tip posted by "Lyn Mac" at the bottom of the first page of the ghudson thread? This code worked for me. (It'd been so long, I'd forgotten about having to implement this "workaround".)

Another idea is to use a multiple-field index (see Access Help file) to prevent duplication of values across a combination of fields. (Note, however, that I agree with maxmangion - it is NOT sufficient to simply use a combination of first and last names.)

Not sure which version of Access you're using, but the Access 2000 Help file has two topics that should be of interest to you: Prevent duplicate values from being entered in a combination of fields Create a multiple-field index To prevent duplicate values in a combination of fields, create a...

The essence of the solution is: implement your audit trail code on the sub-forms. (Remember, sub-forms are only sub-forms when they're placed on another form. If you can get the audit trail to work on these "sub-forms" when they're used as "stand-alone" forms, then all *should* be well in...

From your example, are you really trying to retrieve records where: Provider = '40668' AND Provider = '40163' A single record cannot have two values assigned to a single field. Perhaps you should be using an OR condition instead. This would return only those records where the provider is...

In a nutshell, add the wherecondition argument to your OpenReport command. It should look something like this: DoCmd.OpenReport "[YourReportName]", acPreview, acFilterNormal, _ "[YourRecordIDFieldNameInReportRecordSource] = " & _ Me.[YourRecordIDFieldNameInFormRecordSource]

Sorry - misunderstood. Your PartsUsed form should be a sub-form on your JobDetails form (not your Job form).

Perhaps I'm missing something, but the navigation buttons on your sub-form should do the job.

Umm... You might try looking at the properties for the text box in question. On the "Other" tab, you can specify the Enter Key Behavior.

In the query design grid, the expression for the calculation should be entered in the "Field" box, not the "Criteria" box.

This question has been asked (and answered) many, many times on this forum -- you should try using the Search feature. I believe you'll find the answer is: No; not really.

Here are a couple of links that might be useful... http://www.access-programmers.co.uk/forums/showthread.php?t=41065&highlight=calendar+form Posts 9 and 11 contain examples of calendar generated on the fly that show dates of attendance (or absence!). FYI - once you've opened the Calendar of...

I left out an important bit in my first post - establishing the relationships between the tables and enforcing referential integrity. Once you have created your junction table (tblPlantOwners), open the Relationships window and join your tables: tblPlantOwners to tblPlants - join on...

You should not be storing the plant owners in tblPlants. Create a junction table, tblPlantOwners, to link plants with owners. Your junction table should look something like this: fldPlantOwnerID (the primary key for this table) fldPlantID (the primary key from tblPlants) fldOwnerID (the...

Perhaps the attached will help... one table of people two queries - one last name, the other maiden name one union query - pulling last and maiden names However, this will get interesting when you have people with the same last and/or maiden names...

Let's say you have a Fruit Salad database... tblSalads and tblFruits with a number of Salads that can be created by combining any number of Fruits, with each Fruit available to be used in any number of Salads Your junction table would be: tblFruitSalads consisting of three fields...

Place a Text Box on your report and set its Control Source to an expression that concatenates the two values (question and answer numbers) - something like: QuestionNumber & "-" & AnswerNumber

Sorry jenny23 - I don't want to just abandon you, but I really don't have the time or wherewithal to teach you all you'll need to learn. At this point, my best suggestion is to get a book; perhaps the Access Bible (as listed in the "Recommended Reading List" in the "General" forum).

First off, follow Pat's advice about eliminating redundancy among tables. Then, with your tables straightened out, create two forms: one for your Student data and one for your Register data. Use the Register form as a subform on your Student form.

AFAIK - only if you've stored the date/time in a field with the record. FWIW - I have fields called modDate and modUser in the tables for which I wish to track this sort of information. Then, in the BeforeUpdate event of the appropriate forms, I set these fields to Now() and CurrentUser()...