off2003 with SP2 Update

  • Thread starter Victor_AmericanRiskControl
  • Start date
V

Victor_AmericanRiskControl

We use an Access2003 db linked to Excel2003 table to run queries and manage
jobs in the field.

Since doing an automatic updae (WindowsXP and Office2003) we lost the
ability to edit and write in the table. From the articles on the Knowledge
DB there doesn't seem to be a fix that applies to us.

the other PCs running SP1 still work fine. Any suggestions on how to repair
the 'update'?
 
6

'69 Camaro

Known bug in the update. Please see the following Web page for a wee bit
more info:

http://groups.google.com/group/micr...public.access.*&rnum=1&hl=en#7a06f4e16dfbc6a2

In the meantime, I suggest that you resort to the latest backup of the
computer, because MS Office 2003 SP-2 cannot be uninstalled. For more
information, please see the following Web page:

http://support.microsoft.com/kb/873125

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.
 
V

Victor_AmericanRiskControl

Thanks. One more question. Several months ago I 'decided' to change our
design to split DBs with .mde front ends! Problem is I now know that it was
a mistake. Since we use linked tables anyway it was kinds like peeing in the
wind. I lost my ability to edit my forms and I don't remember putting in a
pasword protection. Is there a way to convert back to .mdb?
 
6

'69 Camaro

Several months ago I 'decided' to change our
design to split DBs with .mde front ends! Problem is I now know that it
was
a mistake.
Click to expand...

There's nothing wrong with creating an MDE front end for distribution. As a
matter of fact, it will prevent most people from fiddling with your design.
I lost my ability to edit my forms and I don't remember putting in a
pasword protection.
Click to expand...

That's one of the benefits of creating an MDE database file. It's harder to
edit the forms and reports, and it's impossible to add to or alter VBA code,
because the VBA source code has been stripped from the file.
Is there a way to convert back to .mdb?
Click to expand...

Yes. It's not cheap, and there are legal restrictions. I suggest that you
find the latest backup of the MDB file and bring it up to the "current"
version of the MDE file -- if you don't have a backup of the MDB file from
when the MDE file was made. "Always keep a backup of your MDB file" is very
good advice -- and cheap insurance.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.


"Victor_AmericanRiskControl"
 
Top