>Hi, everybody!
>Sorry for this VB question in a VFP forum but I assume that
>many VFP developers are also VB guys, so I just try my chances!
>
>This is the VB question:
>
>
> We build a client-server aplication, with Sybase
> SQL Anywhere 5.0 in Back-End and VB5 in Front-End.
> The code has been generate by a CASE tool - PowerDesigner,
> from the DataModel we've created.
>
> Now, we start having this very strange situation:
> the application runs OK from the PC that has been generated
> both the Database and the VB application but if we run the
> application from another machine, we cannot update records,
> instead we got this error message:
>
> Can't update. Database or object is read-only. (Error 3027)
>
> This is what I found in jeterr35.hlp file for this error:
>
> "You tried to save changes in a database that was opened for read-only access.
> The database is read-only for one of these reasons:
>
> · You used the OpenDatabase method and opened the
> database for read-only access.
> · In Visual Basic, you are using the Data control,
> and you set the ReadOnly property to True.
> · The database file is defined as read-only in the
> operating system or by your network.
> · The database file is stored on read-only media.
> · In a network environment, you don't have write
> privileges for the database file.
> · When working with a secured database, the database
> or one of its objects (such as a field or table) may be set
> to read-only. You may not have permission to access this
> data with your user name and password.
>Close the database, resolve the read-only condition, and then
>reopen the file for read/write access."
>
> But none of this possible reasons aplies to the real situation we've got.
>
> Also, on the PC where the application runs, sometimes we got
> a 'Data conversion' error while trying to update a record,
> with no visible reason for having'it.
>
> We are in a verry big rush, actualy we have to solve the
> problem by monday, so if anyone have a hint in that, please
> help!
>
> Thanks a lot,
>
> Daniela

have you tried posting this in the vb area? if not, goto top of screen, use combo to switch to visual basic and click [go]

i'd check the network access to make sure the user has write access.