By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,960 Members | 990 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,960 IT Pros & Developers. It's quick & easy.

Msys Tables -- How do I get rid of them???

P: n/a
Hi:

I just ran an Access application on someone elses system (With Access 2002). I made some
changes (on his system) and then copied the program (data and program are still on the
same file) onto a memory stick and put the whole package back on my system. I now have
some tables I never had before, and cant get rid of them!

They are MysysAccessObjects;MysysACEs;MysisObjects and a number of other tables with Mysis
as the prefix. They are already large, and I want to get rid of them, but am prevented
from doing so because "it is already in use by another person or process". When I look at
the properties, I see that the owner is "engine". Anyone got a clue as to how I can get
rid of these and, even more important, how i can set the other system so they don't get
created in the future?

Regards

and thanks

John Baker
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a

John,

On Wed, 21 Jan 2004 22:31:20 GMT, John Baker <Ba******@Verizon.net>
wrote in comp.databases.ms-access:
I now have some tables I never had before...
No you don't. These are system tables. System tables exist in every
single jet database out there for every single version ever created.
Some system tables exist in all databases (MSysObjects, MSysAces, etc)
and some are particular to certain versions (MSysAccessObjects) or
those with certain contents (MSysImex...), but MSys... system tables
are in every one of your databases - you just haven't noticed before.
and cant get rid of them!


Which is good, because if you could get rid of them, you would have,
and you would have thoroughly destroyed your database and made it
unusable. So its good that Microsoft prevented deletion of most of
these tables (if you look closely, you *can* delete some of them, but
none of the critical ones).

If you want to *hide* these files, go to tools/options/general/show
hidden and system objects and uncheck these checkboxes. Remember that
this only makes it so you don't see these tables. They are, and must,
still be present regardless of whether you see them or not.

HTH,

Peter Miller
__________________________________________________ __________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051
Nov 12 '05 #2

P: n/a
Peter:

Thanks for that advice!

I now notice that I did have the ability to see system files checked in my options (I
believe someone else checked these while testing software). Once I unchecked them the
files were no longer listed.

Being a bit unused to Access I had no idea what I had run into!

Thanks again

John
Peter Miller <pm*****@pksolutions.com> wrote:

John,

On Wed, 21 Jan 2004 22:31:20 GMT, John Baker <Ba******@Verizon.net>
wrote in comp.databases.ms-access:
I now have some tables I never had before...


No you don't. These are system tables. System tables exist in every
single jet database out there for every single version ever created.
Some system tables exist in all databases (MSysObjects, MSysAces, etc)
and some are particular to certain versions (MSysAccessObjects) or
those with certain contents (MSysImex...), but MSys... system tables
are in every one of your databases - you just haven't noticed before.
and cant get rid of them!


Which is good, because if you could get rid of them, you would have,
and you would have thoroughly destroyed your database and made it
unusable. So its good that Microsoft prevented deletion of most of
these tables (if you look closely, you *can* delete some of them, but
none of the critical ones).

If you want to *hide* these files, go to tools/options/general/show
hidden and system objects and uncheck these checkboxes. Remember that
this only makes it so you don't see these tables. They are, and must,
still be present regardless of whether you see them or not.

HTH,

Peter Miller
_________________________________________________ ___________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051


Nov 12 '05 #3

P: n/a
going one step further, during program startup, you can have a function that
sets the application variables to the settings you want. for example:

( For XP )

'View Tab
Application.SetOption "Show Status Bar", True
Application.SetOption "Show Startup Dialog Box", False
Application.SetOption "Show Hidden Objects", False
Application.SetOption "Show System Objects", False
Application.SetOption "Show Macro Names Column", False
Application.SetOption "Show Conditions Column", False

there are different settings for different versions of Access.

John Bickmore
www.BicycleCam.com
www.Feed-Zone.com

"John Baker" <Ba******@Verizon.net> wrote in message
news:0j********************************@4ax.com...
Peter:

Thanks for that advice!

I now notice that I did have the ability to see system files checked in my options (I believe someone else checked these while testing software). Once I unchecked them the files were no longer listed.

Being a bit unused to Access I had no idea what I had run into!

Thanks again

John
Peter Miller <pm*****@pksolutions.com> wrote:

John,

On Wed, 21 Jan 2004 22:31:20 GMT, John Baker <Ba******@Verizon.net>
wrote in comp.databases.ms-access:
I now have some tables I never had before...


No you don't. These are system tables. System tables exist in every
single jet database out there for every single version ever created.
Some system tables exist in all databases (MSysObjects, MSysAces, etc)
and some are particular to certain versions (MSysAccessObjects) or
those with certain contents (MSysImex...), but MSys... system tables
are in every one of your databases - you just haven't noticed before.
and cant get rid of them!


Which is good, because if you could get rid of them, you would have,
and you would have thoroughly destroyed your database and made it
unusable. So its good that Microsoft prevented deletion of most of
these tables (if you look closely, you *can* delete some of them, but
none of the critical ones).

If you want to *hide* these files, go to tools/options/general/show
hidden and system objects and uncheck these checkboxes. Remember that
this only makes it so you don't see these tables. They are, and must,
still be present regardless of whether you see them or not.

HTH,

Peter Miller
_________________________________________________ ___________
PK Solutions -- Data Recovery for Microsoft Access/Jet/SQL
Free quotes, Guaranteed lowest prices and best results
www.pksolutions.com 1.866.FILE.FIX 1.760.476.9051

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.