Hi, Interesting cause I've been thinking latley that I probably drink too much coffee and not enough water. I'd be one to tip the avarage towards coffee drinking ;)

Luc Morin

Hi, Just before I go and reinvent the wheel, I wanted to know if there's such a collection in the .NET Framework 2.0 that could be used as some kind of "Circular list", that is, everytime I want to get a value from it, I get the next item in the list, looping back at the beginning when reaching the end. Thank you

Luc Morin

Hi all, I just wanted to say how happy I am to read all the posts on CP. I'm stuck replacing the night shift maintenance technician in this machine shop, and all I do is wait for problem calls (only had 1 last night). I'm sooo sleepy right now... thank God for coffee:zzz:

Luc Morin

Guffa wrote:

There is no way of knowing for sure what id a record will get until it's created. If you use any method to guess the id (e.g. from the previous records), you might get it right most of the time, but not all the time.

Yes, this is exactly my concern. How do most apps handle this situation ? I was thinking of making the Work Order TextBox invisible until the user actuallty saves the record. What do you think ? Regards, Luc Morin

Hi, First, I apologize if this is not the proper forum to ask my question. I have a .NET 2.0 Windows Form App which uses BindingNavigator, BindingSource and DataSet. The user can use the AddNew and Delete buttons of the BindingNavigator to Add/Delete records to the underlying typed DataSet. In my particular case, I'm showing a Work Order record whose PK is also the table's IDENTITY field (MS SQL 2005). My DataSet is setup with negative increment for this PK in order to avoid clashes. So, when the user clicks the AddNew button, he sees a negative Work Order number showing up until the Update method is called on the TableAdapter. This could be a source of confusion in some users, so I'd like to proceed differently. Should I handle this field manually, getting from the DB the highest Work Order number right when the record is created in the DataSet ? If so, how do I take care of concurrency in the case another user also creates a new Work Order before first user actualy commits his new record ? Or should I simply call Update right away when the record is created ? I assume this is a very common issue in DB programming. Thank for any tips. Luc Morin