David,
I installed the Office 2000 Resource Kit and went to Removal Wizard, but it only shows Files in Temporary Folder for previous releases. How do I use it to remove this version?

"david epsom dot com dot au" wrote:

my PC - but WHAT! I've tried uninstalling and reinstalling Office 2000
(running on XP Home), reinstalling JET, and installing MDAC. I

Use the Office Resource Kit to entirely clean Office off of your computer
before doing the re-install.

(david)

"Laurel" wrote in message
...
Hey boys - stop your bickering and HELP!

I've got the exact same problem that Steven has and if you notice, there
is yet another with the same problem out there with a post "Access Error!"
I still have not found a solution. I can take the db to another PC and it
works fine, so I agree that there is "something" on my PC - but WHAT! I've
tried uninstalling and reinstalling Office 2000 (running on XP Home),
reinstalling JET, and installing MDAC. I don't know what else to do. I've
had this problem for months - just was able to stop using Access for awhile.
But now I'm working on a new app and Access is a great prototype tool.
Created a new DB yesterday and can't go in to design the new table 5 minutes
later. Any HELPFUL ideas??

Laurel

"M.L. Sco Scofield" wrote:

Inline...

"tired, angry, sucidial and bored"
. com wrote in message
...
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.


I guess I didn't go into enough detail. The experiences I was relating
to
did not refer to just one computer.

I started using Access 2003 Beta to do training on 7 computers in my
classroom and 5 machines in my office to test production applications
on.
These machines had different operating systems and *lots* of other
software,
Microsoft and non-Microsoft on them.

When Access 2003 went RTM, I move one of my clients with over 60
machines to
it. Their machines also had a variety of Microsoft and non-Microsoft
software installed.

Both my client's and my machines were a mixture of Win 2000 Pro, Win
2000
Svr, Win XP Pro, and Win 2003 Svr. And we keep them up-to-date with all
of
the patches.

With 72 machines worth of experience on every mixture of software
imaginable
running over more that 8 months on the release version and an additional
3
or 4 months on the beta, when I can say I've never seen the issue you're
talking about, I'm pretty confident that it is *NOT* an Access 2003
problem,
but a specific machine problem.

Like it or not, there is something going on with your machine.


Please don't knock me for saying what a poor product Microsoft Access
is,


I'm not knocking you. I'm knocking saying such a stupid thing with a
total
lack of knowledge.

If Access was even a fraction of as bad as you said, the market would
have
killed Access a long time ago just like it has killed other inferior
products over the past 25 or more years.

Heck, I just took a new machine that won't install Windows 2000 Pro,
Windows
2000 Svr, or Window XP Pro. Are these bad operating systems? I don't
think
so. I'm guessing I have a problem with the computer. Naw, I'll just put
Linux on it. Linux is so much better than Windows that it will surely
install, even on a bad computer...

Ya know, with 1,000's of computers running Access and your computer that
won't, let me try using some logic. Is it Access or your computer? I'll
just
leave the answer to that question to much smarter people than me.


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.


I'm happy for you. I program enterprise applications too. Ever hear of
3-tier n-teir, and .NET? Of course there are alternatives. Dah...

Ever hear of the Java vs. .NET wars? At lease they don't say the other
side's stuff is junk. They fight fair by saying "Mine is better than
yours.
And here's why..."

Access is a desk-top, file-server database. Compare us to Paradox,
dBase,
Fox, or another desk-top, file-server database if you must.

If you want to compare something to SQL Server, compare client-server
databases like Oracle, Ingress, or DB2.

And comparing Access to MSDE is still not comparing apples to apples.
You
should be comparing MSDE to Personal Oracle or one of the other crippled
personal client server products.


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.


I feel for you. I've had to maintain products I didn't like either.


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.


Again I'm proud of you. Ever hear of assembler?


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.


Well Steven, I do respect you for not continuing to hide behind
.


But I guess you paid to play with the Beta copies,


Pay betas? I don't think so. I am a member of a rather public special
Microsoft group dealing with the current version of Access and I am also
a
member of rather non-public special Microsoft group dealing with the
planning of the next version. I get invited to work with the betas.


your whole world seems to be built upon Access 2003 so I don't want to
upset you too much.


I've been proudly using, teaching, and evangelizing Access ever since
version 1.0. You need not worry, I will continue to do so.

Bottom line. Don't go knocking products when your vast experience with
the
product consists of using it on one machine.

Again, I'm sorry you're stuck having to maintain an Access project.

Here's hoping you can get back to your "enterprise" development soon.

Sco


"M.L. Sco Scofield" wrote:

snip