Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What was the developer thinking?
Message
 
 
To
15/07/2009 17:10:19
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01412303
Message ID:
01412586
Views:
49
>>>>I somehow duplicated it 2 days ago. And in my case with even worse result - same ID for two different customers / sales.
>>>
>>>Are you absolutely sure that they are accidental duplicates or fantom records? I ask because sometimes in quoting systems a record is kept to show each quote that was presented to a prospective customer and those records are kept for historical purposes. The changedate makes me wonder...
>>>
>>>There are some times when non-normalized data is required.
>>
>>Attached please find another sample. In the original table I already got rid of complete duplicates (did a select distinct, zapped the table, appended from a cursor) - so these are leftovers.
>>
>>Also interestingly, I see number 01 in the decimal part - I didn't notice this before.
>
>Again, I would refrain from deleting what I thought were duplicates unless I was absolutely, positively, proof-positive that they are indeed duplicates. Are there any child records which might have different information? Perhaps the detail or model number or service was changed but it didn't actually change the price.

As I said, I selected distinct * from myTable - this eliminated complete duplicates (in my own set of data, of course). I leave the other type of duplicates here for now.

I want to be able to replicate this problem and see, what causes it. The customer did identify this as a problem too.
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform