>Ed,
>
>I'm a new Foxpro user, and some of this terminology leaves me in the dark. I honestly don't know how to check and see if the controlsource is writable. as far as permissions - i don't have a clue.
>

First, go top the operating system and check the File Attributes of the .DBF and .FPT files - if they're marked Read-Only, well, there's the easy answer! You canb't write to a read-only file.

If it's a network environment, log into the network as a user with Administrator privileges on the server where the files live. Tf the textbox can now be updated, then the user ID that you'd logged into the network with before didn't have the necessary access to write to the files. Whoever is responsible for maintaining the network needs to ensure that all users who need to add, delete or update the data have the necessary network access rights to do so.

What is the source of the data you're trying to update? Is it in a table, or did you extract the data with a SQL Select statement or via a parameterized view? If it's a table, look to see if your USE statement has a NOUPDATE clause in it. If the data was extracted with a query of some sort, the cursor that gets created can't be written to without a bit of trickery, and even if you can write to the cursor, the data won't be propagated back to the data table it was pulled from. If you're referencing a View defined in a database container, make sure that the view has been set up as updatable - the view definition has to allow the data to be written back to the table, and you need to specify which fields are allowed to be updated.

>
>>>Why would a textbox be readonly if the property "readonly" is set to False, the data type in the field it's bound to is Currency, and the checkbox for readonly is not checked in builder?
>>>
>>
>>Is the control source writable? If you're using a non-updatable view, a read-only cursor (one created via SQL Select without going through a little trickery to reopen it as writable), the table was opened with the NOUPDATE clause, or the user doesn't have sufficient permissions to write to the table, the problem could lie there.
>>
>>Then you get into properties - is the textbox enabled? Anything in the When event that doesn't permit you to select the textbox? Is the textbox in a containership hierarchy, where a higher-level container might be set as read-only?
>>
>>What happens if you delete the textbox, readd it by hand and set the properties?
>>
>>>Thanks ahead of time,
>>>JD