For example if during a Sales transaction where there are many articles being scanned and one have been scanned twice by wrong manipulation of the sales person, I clicked on the row which have been entered twice and key in Delete on the keyboard. It won't go away
Normally in a POS when an item is scanned/sold, the item is removed from inventory in some manner. I would suspect that this is the underlying cause as to why you can not simply delete the duplicate sale... you need to add that item back to the inventory. Hence my position in
post#10
SO within this thread, we can take a look at how to back out the "transaction" by streaching the question a tad by looking at the code behind the "sale." Understanding how that record is created is importaint to understanding how to remove the record; thus, "deleting" the record as requested. Otherwise we're looking at a new thread.
So, let's start with your database design at a high level view, what I have so far is:
tbl_customer : this table has the details behind your customer
tbl_sales : relates the tbl_customer to the product sold in some manner.
tbl_? : the other tables please and how they are related.
We then need to see the code and sqls behind the "Sales" transaction. It is realy very poor programming to not provide a "LineItemVoid" and "VoidSale" even the old mechanical cash registers could do that!
Before posting any of your code, sql, etc... please do a few things.
1) make sure you have a backup of the production database.
2) make a second copy for us to use as a development database
3) read thru
>> Before Posting (VBA or SQL) Code.
4) read thru
Database Normalization and Table Structures.
5) answer
Post#8
6) which version of Access are you using
#3 and 4 are essential for you to understand as these are the core upon which most of the experts on-site start and it will help you to understand us.
#5 and #6 are essential in that any solution we may comeup with will vary based on these conditions.
Until we have this information, this thread is stalled.