After note :)

I took my notebooks home last night and went searching for what possessed me to ever look at generating my own key n the first place. Seems the data warehouse has more tables then I can track of anymore ;)

There are 3 transaction files in all this data that are different from the rest, and diff. from examples i used here unfortunately. I was looking at generating my own PK in order to avoid completely re-populating these transaction tables every day/month due to the size of the data at the time. (plus this data comes in already denormalized, and doesnt need to support any relatinal processing). As the app has evolved, only 1 of the 3 transaction files comes into regular use anymore, and it's size decreased significantly once the sales markets began selling products/services other than just beepers. But I had forgotten I had this exception in my data, and I'm going to need to add to my Data Handling process so that the new way will be more efficient when it has to work with a non-relational transaction file. So I will reap some value from this thread and your suggestions in the next gen. of my app. Thanks again for your input!