I support an order entry system. Someone creates an order which makes an entry in the orders table. Then they add details which go to the order details table. A key in the details table is the order number.

A user said that she entered her details and then went back to look at the order, they weren't there.

I looked at the details table and it appeared that she had entered 3 details. When I set the order on the details table to the order number and used browse key 'order number', I saw 3 records, but the first was completely blank. The code in the routine that displays an order does a seek on the order number and then reads each detail in sequence until the order number on the detail is different. Since the first one was empty, it stopped the display and made it look like everything had been lost.

We have had a number of issues since the work stations were upgraded to Windows 10. An earlier issue seems to have been resolved by not using the Windows mapped drive 'feature'. We were getting numerous read errors when addressing the tables via a Windows mapping. Since making that change, we have reindexed the tables - the above issue happened after that.

Thanks for any ideas!