I was using the free download evaluation (Personal Edition) of UniVerse 10 to test record locking and displaying an appropriate message to the user.

To test record locking, I had to log in twice – oops – the personal edition is single user. It is a good policy to release an edition which is single user when one of the prime functions of database activity is multi-user record locking accessing?

Coming from a generic PICK background, I have not had significant experience in the new READ statements in UniBasic like READL etc. I will have to put some of my experiments on the back-burner until I get an opportunity on a clients system.