I have a sales order database with a serialized field that auto-generates a sales order
Number. The sales order table contains about 25k records and there are about 15 records
That were created with an asterisk preceding the sales order number, they are still in
Proper sequence but just contains the asterisk at the beginning. The field is a key field

And the issue has propagated to my other related tables.

 

Has anyone ever seen this issue?

Database hosted on FM 11 server, Mixed clients 10 & 11 all windows.

 

Thank You

Anthony
 

Hi Anthony,

 

I've seen it 3-4 times (never with my solutions, knock on wood) and the reason has always been the same ... at some point on some layouts, the primary key was left open for User entry.  And a User decided to flag their special records with their own special mark.  That may not be the reason but it would be highly suspect in my book.

 

Also, do you ever import records?  You say the 'Sales Order number' but is the field a number or text?

It also looks like it might be something a User would do when attempting to find all records with a value in that field.  *  that maybe they were in browse and thought they were in find.  But there wouldn't be a need to search for 'all' on a primary key; at least not by a User.

Laretta said ... "It also looks like it might be something a User would do when attempting to find all records with a value in that field.  *  that maybe they were in browse and thought they were in find.  But there wouldn't be a need to search for 'all' on a primary key; at least not by a User.". 

 

I would add that if users are given the ability, even in the face of clear visual clues, outright warnings, and repeated training, they will do stuff that defies logic.

Thank you for your replys. The field is a text field and is not open except for finding on any of the layouts.

A strange one indeed. What do you think about selecting this option in the field definition?

 

 

Thanks again.

Good for you, Anthony!  Yes, and I meant to mentioned it as well.  I was focused on identifying the current hole but, if you cannot guarantee  protection then this option will protect for future. 

 

Indeed, Kris, and some Users enjoy hitting all keys just to find out if there are ways into something they shouldn't be in.  Security with tight privileges are always in order.  :-)