Hi everybody,
        I finally found the solution to my problem with the help of Thomas, after
an update of the server version or after recovering from an old backup, one
should always issue a load_systab command in dbmcli. Here is the exact
syntax from the create_demo_db script:

dbmcli -d %SID% -u dbm,dbm load_systab -u dba,dba -ud domain

I am happy to found that the problem was my own mystake, execpt that little
episode, sapdb has been up for more than 220 days with 100% availability
(OLTP with 30 concurrents users, linux server).

Good luck!

Yves

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Yves Trudeau
Sent: 10 juin, 2002 16:57
To: SAP DB General List
Subject: MS Access and primary key


Hi,
        I just upgrade my database server from 7.3.0.20 to 7.3.0.24. We use an MS
Access 97 application which do a refreshlink upon startup to connect the
"linked" tables with the correct user rights. With version 7.3.0.20, the
refreshlink import correctly the primary keys of the tables but with
7.3.0.24, no primary keys are imported. This causes the MS Access forms to
be read-only. This is quite troublesome since I failed to downgrade from
7.3.0.24 to 7.3.0.20.

Any suggestion is welcome,

Yves Trudeau

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to