>1. updating RVs onsite requires users to logout making them irretable.

Give each user a local copy of the DBC. Deploy your views as .PRG files. When ever you need to use the view, you run the .PRG then USE the view. This will allow you to update the .PRGs without the user having to logout. You should also mark the DBC and the PRGs as readonly so they won't get use locks on them.

>2. for unknown reasons, key fields sometimes resets as unchecked causing unsuccessful updates.

Um... well, this is probably due to your code, I can't see this 'spontaniously' happening. But, once again, making the DBC read-only should keep changes from happening.

You may want to turn DBC events on and see if you can capture what is changing the primary key setting.

>
>How to get rid of the above problem folks? Or is there really a solution?

You could go to CursorAdapters. Since they are stored in code the should be alot less fragile. Although, we never had your problem 2 happen to us.


BOb