Ummm,

How does the fact that Access 2003 works fine on your computer help me, or anyone else on this forum with the same problem ? All that implies is you haven't done something to your installation, perhaps you don't have administrative rights over your machines, perhaps the Windows Updates aren't installed etc...

I can install Office 2003 on a new machine and it works fine until the updates are applied, then it mysteriously stops working, but it's the only part of Office that fails, Visio, Project, Word, Excel, PowerPoint, OneNote, Publisher and FrontPage work just fine.

Please don't knock me for saying what a poor product Microsoft Access is, I program enterprise applications that Access cannot be used for, hence the need for SQL Server. Do you wonder why there is an alternative to Jet in the form of MSDE for Access. MSDE is a 10 user / thread constricted version of SQL Server.

Unfortunately, in this case, a database has been provided for me to maintain, I can install a previous version of Office and that works OK.

But being a very well heeled C++ developer, I am able to see where the problem is, I understand the guts of Office and the Windows Template Library, in which, most of Office is written.

Oh, my name is Steven Redferne, just for the record, I opted out of the Office 2003 alpha developer testing after the amount of time Office XP took. But I did do some work with the XML schema definitions.

But I guess you paid to play with the Beta copies, your whole world seems to be built upon Access 2003 so I don't want to upset you too much.

"M.L. Sco Scofield" wrote:

Too bad that you don't have the guts to identify yourself when you decide to
bash a fine product like Access 2003.

I've been using Access 2003 in both production and in all of the training
classes that I've been teaching since Beta 2. I have *never* encountered the
problem you are describing.

I've had Access 2003 running on Win 2000 Pro, Win 2000 Svr, Win XP Pro, and
Win 2003 Svr.

Having used Access 2003 Beta 2, RC, and RTM on 4 different operating systems
without encountering the problem you describe leads me to believe that you
might have some *other* issue going on with your computer. You aren't
current with all of the updates. You've got some third party program
misbehaving. You've got a virus. Or who knows what.

Here's hoping that your uninstall of Access 2003 went well.

Sco

"tired, angry, sucidial and bored" tired, angry, sucidial and
wrote in message
...
I have seen in other posts where Access 2003 displays a box showing
"Unknown"

I'm getting the same error, so I thought I'd do some investigation.

The error is caused by a jump by MSACCESS.EXE into DLL entry point that
doesn't exist.

The Unknown error seems to be a catch all error message for unhandled
exceptions such as this.

This is the first time I've used Access 2003, I tend to avoid Access at
all costs, prefer to use SQL Server.

I decided to attach a debugger to Access and catch the original exception,
ah ha, "Class not registered" - so there is something missing.

I've tracked down a problem in the VBA routines which so happen to be in a
bunch of DLLs that have been recently modified.

I wonder if Microsoft have been naughty and are calling directly into the
DLLs rather than using their vector tables...

Looks very silly when you create a new database and you can't open it
again.

Not holding out any hope of Microsoft sorting this problem out...
thankfully I have more than one computer... I'm removing Access 2003 from
this PC, no point in having it if it doesn't work.

BTW:Access was rubbish until Microsoft "bought" FoxPro and Fox Software
and got the Rushmore technology.... Anyone for some Sybase - SQL Server ?