Access 2000 to 2003 upgrade = recordset is not updatable

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Peter B. - 21 Nov 2004 09:50 GMT

Tested moving application in Access 2000 to Access 2003

Access 2000 - Office XP on Windows XP
Access 2003 - Office 2003 on Windows 2003 Enterprise Server

Application first written in Access2.
Upgraded to Access 95.
Upgraded to Access 97.
Upgraded to Access 2000.
Additional objects added throughout the upgrades.
Existing objects modified.
Issues created from previous upgrades identified and resolved.

The data tables are in a separate mdb file located on a file server.
All other objects are in a second mdb file distributed to multiple desktops.

Tested upgrading to Access 2003.
This resulted is being unable to add new record or edit existing record in
any existing form.
The department has shelved plans to upgrade Office 2000 to Office 2003 until
matter resolved.

Action:
Click a command button with following code:
Me.RecordSource = "tblDailyNorthEast"
DoCmd.GoToRecord , , acNewRec

Result:
Returns the following error:
Run-time error '2105':
You can't go to the specified record.

Also read in status bar:
This recordset is not updatable.

Comments or assistance in this matter is appreciated.

Reply to this Message

david epsom dot com dot au - 26 Nov 2004 02:21 GMT

Every time anyone has ever asked me about this problem,
it has always been because the data file was read-only.

> Tested moving application in Access 2000 to Access 2003
>
[quoted text clipped - 32 lines]
>
> Comments or assistance in this matter is appreciated.

Reply to this Message

Peter B. - 28 Nov 2004 06:15 GMT

Thanks. That is the problem. Not certain how to undo this read-only setting
though.
Considered the options in the following link
http://office.microsoft.com/en-us/assistance/HA010345391033.aspx,
but none applied. I have two lab machines, both with Windows 2003
Enterprise Server and Office 2003 plus SP1 installed plus several other
applications.
The principal difference between the two servers is one has MSSQL 2000 SP3
and the other has IBM DB2 v8.1 Enterprise.

The MS Access database application was installed this past week on both
machines.
The result was the data application was fully working
on the MSSQL box, and read-only on the IBM DB2 box.

Is there some security setting that may be interacting with MS Access?
Any other thoughts are welcomed.

Again thanks for the help.

> Every time anyone has ever asked me about this problem,
> it has always been because the data file was read-only.
[quoted text clipped - 37 lines]
> >
> > Comments or assistance in this matter is appreciated.

Reply to this Message

david epsom dot com dot au - 29 Nov 2004 00:41 GMT

Access uses the file-server database semantics, so it
is subject to your file-server permissions. You can
check that your user has permission to add/edit/delete
a text file in the database folder. If that works,
try getting your user to copy the database file (to
change file ownership), and see if that helps.

(david)

> Thanks. That is the problem. Not certain how to undo this read-only setting
> though.
[quoted text clipped - 15 lines]
>
> Again thanks for the help.

Reply to this Message

shawn.stanaland@ngc.com - 14 Dec 2004 14:09 GMT

It almost sounds like there is something wrong with the
links. Did you try a refreshlinks?

>-----Original Message-----
>Tested moving application in Access 2000 to Access 2003
[quoted text clipped - 35 lines]
>
>.

Reply to this Message