Do you have other programming that make those elements writeable or that sets the value in those elements?

This morning when I got here the item name element had two dots in it, the item number was empty, all the other elements were populated, the item number field is readonly and grayed out, how they blanked it I don't know???    I have been trying for over a hour to duplicate what happened yesterday to no avail.

Poppy,

the following works for me in my inventory database (and keeps the users from accidentally stepping on an ItemNum with ".." search attempts while in 'update' mode).  It allows the ItemNum to be written to if in Add or Search mode, but not in Update mode:

ItemNum:nElementEntry ...

If (@mode() = 1) AND (@IsBlank(ItemNum) = 0) and (FixOKd <> 1)
     {
           ReadOnly(ItemNum,2)
     }


I also have code to make ItemNum writable for modes ItemNum:nFormReveal, OnFormChanges, OnFormEntry, and Inventory::Retrieve Spec Open with the following  code:

If @Mode() = 2
 {
     ReadOnly(ItemNum, 0)
 }


My users do not have access to the side panel, and must utilize on form command buttons (preferable) or function keys (old habits).  I try to have my users save a changed record by having to use a command button to save (instead of F10, which I disable temporarily with the following code), as I have other housekeeping that is checked/updated when a record is changed in Inventory.

Inventory:nFormEntry

If (@Mode() = 0) and @IsNew
 {
     IgnoreKey(KEYCODE_F10, 0)
 }

If @Mode() = 1
 {
     IgnoreKey(KEYCODE_F10, 0)
       NotifyForm(7)
     
 }

If @Mode() = 2
 {
     ReadOnly(ItemNum, 0)
     ClearIgnoreKey(KEYCODE_F10)
 }

and on Inventory:nFormExit and Inventory::RetrieveSpecOpen

ClearIgnoreKey(KEYCODE_F10)


Hope I'm not steering you wrong.  The above arrangement works for my users beautifully.

ps (I have a 'fix' command button that allows ItemNum to become writable in update mode in the event I need to change something in the ItemNum or ItemCategory designation).

I don't know if this will apply in this case, but I used the AppSaveMode() command for a purely historical database. The command prevented the addition of any new records and the deletion or alteration of any records. It works for me, but may be overkill in your situation. It's important to make sure it gets toggled back to normal after it's no longer needed, however.