Thanks for the response sjstamp... I also thought of renaming the Scott #'s for Kathiri and Quaiti. I'm sure this will work. However, I have two big problems with this. First, this is simply a bandaid for a problem with StampManage. In a relational database, you can query for data using search criteria on specific fields in the db. In this case, if you simply query for "Country = Aden" and "Scott # = 1", the resultant data would be Scott # 1 from Aden, Kathiri or Quaiti (ie. three values returned). Obviously a problem... However, if you have a 3rd field where you can specify "Aden", "Kathiri" or "Quaiti", then you will get the correct result. This will allow the Scott #'s as published by Scott to be used without modification. Personally, I do not want to get into the business of keeping track of which countries I modified the Scott numbering system in. I am fairly confident that Aden is not the only example of this problem with the numbering system.
Secondly, if you implement this system of modified Scott #'s for Kathiri and Quaiti, what happens down the road if StampManage fixes the problem and releases an update which uses the correct Scott #'s? Actually, I need to understand how this works for all updates. For example, if I add a stamp to a country where the Scott # did not exist in the country and later a StampManage update adds this stamp, what happens to the entry I made? Is it overwritten? Again, if I have entered a number of stamps in several different countries and an update occurs, how do I know what has been modified?
In conclusion, I would like to see the problem fixed in a fashion where the Scott #'s do not need to be modified. I have enough problems keeping track of stamps without having to refer to a cross reference table. Whether this is accomplished be modifying the queries to add an additional search term or by treating Kathiri and Quaiti (for example) as a seperate country (or some other method), the main objective should be to maintain the integrity of the Scott numbering system.
I've had a question in the back of my mind about StampManage. Since it is licensed by Scott to use the Scott numbering system, why are all the Scott numbers not in the DB. Surely Scott could have provided a basic file with all the numbers for every country which would include basic information such a description, perf, color, etc. They could even provide the pictures. Now I suppose it came down to a matter of money. The more you pay for the license, the more data you get. I don't put this pass Scott. They do have an investment to protect. And... this may be purely conjecture on my part.
Anyway, I am going to hold off for awhile to see where this goes. Hopefully, we'll end up using the Scott #'s as they are.