Linked MS Access table Not Updateable 2

[mcelligott]

I have linked a table from one MS Access 97 database to another MS Access 97 database. Unfortunately the linked table is not updateable in the other database. I have been reading through the forum for any insight. I have made sure that the original table has a primary key and it has several indexes. The database itself does not have a password, it is setup with user-level security. Am I missing something here?

Thank you in advance for any and all anticipated help.

 

[BKoops]

Darn! wish the workgroup thing could work for me! Anyway, Annsolomon mentioned Service Pack 3. Does any of you know where to find this? I can't seem to find a Service Pack for Office 97 later then 2b.

 

[annsolomon]

Sorry, BKoops. I live in an Office 2000 world and was thinking about that when I mentioned the service pack. Can you give us any more details about your situation? (e.g., exactly what's happening, when, where, etc.)

And, as I previously asked Bob, what version of 97 are you runing. What version of Jet?

Ann

 

[BKoops]

I'm running an application which is based upon Access 97. To run this program you need Access 97 and we have install 97 2b. Unfortunately, the requesting party lacked the view to have this application made in Access 2000 so we now have two MS Office's running on the system. (grrr)

Thing is, as an administrator of the package, some members have to change certain fields. This has recently resulted in the error 'record-set is not updateable'.

Currently, I know I still can change what has to be changed on a newly prepped system (!!) with the same account. However, after some time the same problem returns. So I'm going to compare two systems and try to find a false where should be a true (or the other way around...)
Hopefully, I'll have this cleard by the end of this week.

 

[BKoops]

Well, call me buggered... it now seems the workgroup problem was the problem I experienced to. However, it was pretty strange.

Via wrkadm.exe I could see the right workgroup and see I was a member of it. However! Somehow this was NOT written to the registry hkey_local_machine\software\microsoft\office\8.0\access\jet\3.5\engines

but into the key of office 2000!

hkey_local_machine\software\microsoft\office\9.0\access\jet\4.0\engines

Logically, this can never be. wrkadm.exe doesn't write to the later versions but it did happen by some strange kind of fluke. I had to fully enter the data with wrkadm.exe again (and no viewable change) and then could again update my records.

It's just a theory, but I think the problem lies with another Access based application we're running in our company. To have this installed, you have to run an update of Jet for Office 2000. I suspect this may have caused my problem.

 

[annsolomon]

Hi, BKoops. Or, should I call you Super Sleuth?

Great troubleshooting, bubba. Glad you figured it out!

Ann

 

[Casala]

HELP - can I reopen this thread, BKoops - I need your help, I have a horrible feeling something similar has happened to me - what/how did you do/change to make your database able to be maintained again.

Your explanation of what you did is totally foreign to me, please help.......

 

[mcelligott]

Hi Casala,

If you are having this same problem. It should be an easy fix. Personally I would still be having it if it weren't for Ann's solution. Try this:

- Find the following file: WRKGADM.EXE (it should be in the following directory: "C:\WINNT40\system32\WRKGADM.EXE" or something like it).
- Double click on this file (a dialog box will display)
- Click JOIN
- Click BROWSE (then find the mdw file that the original database you are linking to is using and double click on it).
- Click OK
- After it says that you have successfully joined the workgroup, click EXIT

You should be all set now. Hope it works for you.