>Kevin, I'm doing my own numbering now by finding the Max ReqId number and incrementing it in code and using it as the default, this works better and removes the problem.
>
>Mike, to answer you, my PK is my Requistion number which has to be unique anyway and how my users normally find records along with a multitude of other ways, so I display it, and I am also in testing stages and I want to see what's going on. They also use the P.O. number, vendor, etc. to find records. The Req number gets put into the line items and the receivers (with their own ID's). This .NET application is comming from my FoxPro application, so the Req numbers have to come over, too. It's my FP mentality and general SQL ignorance. FP is not officially supported here any more.
>
>On the private side, glad to hear from you. Heard the heat was miserable there. The weather here in August this year has been great, June and July were not the best. Dick is so busy in the ER he hasn't been doing much FoxPro work, and we can't even get together for lunch. We manage to talk a bit when we meet by accident getting coffee. We are in a major building spree here, adding on a Women's and Children's hospital building, another parking ramp, and general expansion of some departments.
>

With you and Dick unable to get together for lunch, the nearby Indian restaurants must be dropping like flies!

It's good to hear about the expansion of the hospital. For a backwater state Maine does some things very well, and Maine Med is one of them.

FWIW a little trick I use is to set a developer flag during app startup which controls whether certain fields are visible, enabled, etc. I set the flag based on a Windows environment variable, although obviously there are other ways to manage that part of it.

Yes, the heat has been miserable here (and most places) for most of this summer, but it's been gorgeous the past several days. Before we know it, it'll be cold again, so no complaints from me.