Search results

Hmmm...I appreciate your insight. Thanks for sharing. For each transaction, there may be anywhere from 1 to 1,000 cards tied to a specific transaction. This would certainly cause a problem wouldn't it? Because if I had a FK for card ID in my transaction table, what would I do if there was...

Nope. I keep looking for something but can't find any difference.

This really is weird. I just was going through some of my backups and I had the exact same query and I'm able to add values left and right. No problems at all...why all the headaches with this one?

Nope...nothing going on there. Hmmm...this is tricky. Again, thanks for your help. I can't wait till we get it figured out! LOL I'll keep trying things

Yes I did n the weird thing is it won't let me put in any transaction number I haves saved in my table

Ok...thank you for your help! So, I went into my table (Transaction ID) and simply clicked the Primary Key button which took off both PK's on the two fields. I then went into my table relationships and everything looked the same. No changes there right?? Would taking the PK's off this table...

and some more

Here are some screenshots.

Here are some more attachments.

Thank you for taking the time to help me. I appreciate it. Here are a lot of screen shots that hopefully explain better than I can in words what is happening. Thanks again.

LOL I'm sorry for confusing you. I'm talking about the query in datasheet view. I'll try and post some shots. I found one way...I'd have to go back to the table from which is the field is, and take off my primary keys that way I can have null values. Once I go remove the values for the...

I entered the value in datasheet view.

http://www.access-programmers.co.uk/forums/showthread.php?t=220352 I wrote a novel here...hopefully you can see where I'm coming from. Thanks

I have three tables. The 1st table is for the sports cards. Each record is an individual sport card and the various columns and fields give detailed info about each record (card). The 2nd table is for my transactions. Each record is a specific transaction whether is a card sale, card...

Nope...I can get to the design view of the query.

I accidentally entered a value in a query, that may at some time have a value but doesn't as of yet. So, I need to get this value out but it won't let me know because it can't contain a null value? Any tips? I want this to go back to being a blank value I believe, but it won't let me because...

But, here's the deal. After I exit out of these forms, if I go into my table for Transactions, the new record with transaction ID #105 is there saved. So, then when I go back to these forms when I know the record is saved, it still says the row hasn't been committed. How can it not be when...

LOL yea by the time it took me to write it all out I figured out what I needed to do

Right on...thanks for replying. I think tho with years...I'll run out of values because I could possibly go all the way back to the early 1900's and of course each new year will also probably be added. Thus, at some point I'll run out of room so I'll just do a table.

Stupid question...I might as well delete the thread. I just need to go into my original table and set that specific field to lookup the new table and not the value list anymore. Sorry...