Search results

I agree. An example db might help. However, to step back a little: The goal of this database is to record the grades of students, correct? And all students take a range of classes? So, we obviously require a table that lists Students and a table that lists Classes. tblStudents StudentID...

Yeah it can be a pain. That's probably how Spore wound up the most pirated pc game in 2008 too :(

Well, to give due credit...Bioware just announced their next big game, Dragon Age: Origins will feature a return to simple disk checks without the malware and online activation requirements. :D That's two thumbs up from me :)

I love my ipod Touch. No At&T bills but all the apps I can eat. :)

Ok, so you want to remove the null field3 records only if the Serial number is duplicated? Create a calculated field in your query that has something like: IsDuplicate: DCount("*","TableName","[Serial_Number]=" & [Serial_Number]) Then you could set two criteria rows in your query...

Have you tried using a criteria in Field3 to remove records without information in that field? i.e. Is Not Null

LOL :D I know the feeling far too well... Glad it worked for you :)

Ok...now I see the problem. Recall that your dlookup has a a bunch of conditions that it is looking to meet in the table "All_Dryer_Belt_Transactions". You have it looking for fields in that table which are simply not there. You have joined to those fields in your query, but the dlookup is a...

If no one sle gets to this, I'll download it tonight and look at it at home where I have AC2003 (I only have A2K here at work)

LOL I guess so. His was much fancier though ;) I guess that's why he gets the big bucks, eh? :)

Silly question here: Why not make a master copy of the database, and give a disposable copy to each person you want to train. Let them train with it...then throw away that copy. Your master never gets edited.

Oh, sorry, I thought you had asked what the errors were originally. My mistake.

I'm glad you found a solution that works for you. Thanks for posting your final solution for others who might come across this thread in the future. :) One thing I would say is that I personally would probably not take this approach. In order for this work, you are automating the data entry of...

Hmm. No. I think you missed some of what Paul was saying. You have a main form: Either bound to events, or to People. Let's say you bind it to Events. You have a subform bound to Junction, inside the form which is bound to events. Now, there is an EventID field in both Events, and in...

Note: this post is a response to Brian's earlier question....not to the code you've used most recently. I have no idea why the syntax would work in your test db and not your production UNLESS there's something screwy in the real data like some alphanumeric values or nulls where there should only...

I typically avoid this by using the on_enter event of the subform control (the container for the subform, not the subform itself) to check to see whether the pk on the parent form has a value or not (if it does, there's a parent record....if not, then I change the focus to the first...

I think there was some erroneous syntax... The normal form for Datediff is =DateDiff("increment here","[FirstDateFieldHere]","LastDateFieldHere") Prod1_5: sum(iif((Datediff("d",[2]![CREAT_TMSTMP],date())>=1) And (Datediff("d",[production date],date())<= 5),1,0)) Hopefully that works but...

You would put the example I gave as the control source for an unbound testbox on a form which is bound to your customer table. Whenever you change records, the textbox would show you the alpha numeric form of the id. Or you could use the same logic in a calculated field of a query which uses the...

I agree with RG. An autonumber is what you should store in the table as your CustomerID. Any time you need a 'special' id code, you can always calculate it on the fly using something like =Left([Surname],3) & Format([CustomerID],"0000")

Hmm. Couple of things: You do not need to qualify the table every time you reference a field in that table in a domain agregate function like Dlookup, DMin, etc. The second parameter in the function IS the table or query reference. Note: If you are using this expression in a query, and the...