>Hi Borislav,
>
>PK is an integer. Since I bring down all records in that table, if there are any, I find the max interger and add one to it, to get the next pk. Then add one to the new number as I go through the records I have on my side of the equation (i.e. the records to be added to the table). if no records in the table from server, I change the pk in my tables starting at 1. Hope that makes cents. :-)
>
>This is a conversion program, so most time (if not all), there should be no records in the tables I am accessing, but, just incase, the code is there.
>
>Anyway, I finally got it working, but I am not sure exactly how, because I made many changes trying to get it to work, the last change was putting oRS.CursorLocation to client. Now things get into the tables and I was able to check it in.
Beth,
This approach can only work in a single-user application. In multi-user application it is not safe to get PKs this way.
If it's not broken, fix it until it is.
My Blog