Recent content by CBenfer

OK - that seemed to fix everything up. Thanks very much for the help!

I'm on the same PC.

OK - I had a database that was working pretty well on Friday. I opened it up to test something today and all of a sudden my form stopped working. It is a simple form - see attached photo for the form view. When I click on either button I get the error in the attached JPG. Here is the code for...

Hey all. I don't know if this is something realistic or not, but here's what I want to do: I will have a PC and a number of scanners in a production line. I will need at least 15-20 scanners and would like to plan for more if needed. When an operator clicks on a button I would like to have...

OK, I played around with looking at the string and it looks like it has to do with the way I'm storing one of the fields. It is supposed to be text, but somehow the leading "0" if I put in "060" or something like that is being truncated. I'll see if I can fix it, otherwise I might be back...

Well, the reason SpecID is not a Variant is because it should never be Null. I just added the record, so there HAS to be something there that matches, right? Or have I just looked at the code so long that I'm missing something dumb? For reference, sSpecificationID is an autonumber field. I...

I'm sure I'm missing some sort of parentheses or something simple, but here goes. I'm trying to run the code below. The basic idea is that I need to insert a record into a table and then return the Key field so that I can use it to populate another table. This was working just fine for a while...

Sorry, A and B referred to my original post - I thought the labels would be less confusing. On the query - how are you building it? When I tried something similar I got an error. Are you using the query designer, or writing the SQL directly?

Either the "A" or "B" field above should work fine. Is there a way to do that in one query? I managed to do it in two, but I'm guessing there's a better way to get it done.

Either would be fine. I used the autonumber field, but the date/time stamp would work as well.

For what it's worth, I have a workaround in place for this at the moment - I created a separate query that pulled up the last nine records that met my criteria, then ran my query to get the number of "Increasing" values off of that query instead of directly from the table. Probably not the most...

OK all, I think this should be relatively easy, but I'm getting myself confused. I have a table with: A dDataID (sequential auto-number) B dDateTimeEntered (date/time field) C dFactoryOrder (text) D dSpecificationID (number) E dStartWeek (text) F dIncreasingDecreasing (text, values are limited...

I was trying to think of a better way to describe what I wanted in the last post, I came up with a different thought entirely. If I don't allow records to be deleted from the specification table, there is a many-to-one relationship between the data storage table (which contains info for a given...

I'm not sure. Each part should only ever refer to one specification at most, but it can refer to no specifications if the spec has been deleted since the part was run. From what I can tell, Junction tables are typically used for many-to-many relationships, but you might be referring to a use...

I looked in Relationships and I see where you have it connected, but here's my problem: As a user, I'm going to input certain features of the job I'm about to run - Part Number, Sequence or Operation Number, and Measurement Name. From there, the system is going to need to look up the correct...