Ozair
If John's utility doesn't fix your database the only 3rd party vendor I'd recommend is http://www.everythingaccess.com/
Regards,
Bill
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of ozairkhalid@hotmail.com
Sent: Wednesday, November 20, 2013 10:01 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] RE: MS Access 2003 bloating excessively
Bill,
You are right, I tried that too.
I am suspecting there MUST be some network issue.
If this is not against the protocols of the forum, could you please recommend some 3rd party vendors for
MDB corruption? I googled a lot but don't exactly know if they will really work.
Ozair.
---In ms_access_professionals@yahoogroups.com, <wrmosca@...> wrote:
Ozair
In my experience it is best to link the tables first and then IMPORT the other objects into the new database. Exporting must be one object at a time unless you write code to do it or use my ExportAll add-in in our Files>Utilities and Addins folder.
---In MS_Access_Professionals@yahoogroups.com, <ozairkhalid@...> wrote:
Hi,
Hopefully I am able to resolve this by...
- exporting all objects into new MDB ( excluding linked tables )
- then re-linking tables by recreating new DSN-less connection from scratch.
The process is underway, I will share the final outcome once finished.
Ozair
---In MS_Access_Professionals@yahoogroups.com, <ozairkhalid@...> wrote:
John,
Yes I did that too.
Today I am going to try SaveAsText and LoadFromText.
Question : ( aside )
I was googling this and saw Allen Browne's post. ( very old )
http://www.pcreview.co.uk/forums/msyscompacterror-strange-error-recorded-t3046870.html
While suggesting a solution he said "Is there lots of free space on this drive?" - I do not understand it - could you please explain?
Ozair
---In ms_access_professionals@yahoogroups.com, <JohnV@...> wrote:
Ozair-
Have you tried importing everything but the linked tables? The error about MSysRelationships implies it's having trouble mapping the SQL Server relationships into Access. That won't happen if there are no linked tables. Do you have any local tables?
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of ozairkhalid@...
Sent: Friday, November 15, 2013 12:25 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: RE: RE: RE: [MS_AccessPros] MS Access 2003 bloating excessively
Ahmed, Thanks for the link.
@John,
Yes I have tried multiple times to re-build the application by importing all objects into a fresh MDB.
Even in the new file, the auto generated table MSysCompactError appears always with some new values.
I have been careful to uncheck "Track Name Auto Correct" every time.
It is becoming challenging because I am still not able to isolate the corrupt ( if any ) object including custom menus.
Did I tell you I have just re-installed MS Office 2003 with SP3 + Hotfix then ran windows updates.
Ozair.
---In MS_Access_Professionals@yahoogroups.com, <ahmedhashim1@...> wrote:Ozair-,
Also besides what John and other master of Access said, you may want to check this link:
http://stackoverflow.com/questions/15830981/what-is-the-best-way-to-prevent-access-database-bloat
Regards
AhmedJohn Viescas <JohnV@...> wrote:
Ozair-
It sounds like your database is corrupt. Try creating a new empty database and then import all the objects into it from the broken one.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of ozairkhalid@...
Sent: Friday, November 15, 2013 8:22 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: RE: RE: [MS_AccessPros] MS Access 2003 bloating excessively
Also
Linked Table Manager throws "Application Defined or Object Defined Error"
Ozair
---In MS_Access_Professionals@yahoogroups.com, <ozairkhalid@...> wrote:Hello John,Bill and Gary
Thanks for your input.
I am still struggling and still unable to resolve.
Things I have tried...
#1- deleted all linked tables then compacted the MDB.
there was a new table automatically created with two records.
Table MsysCompactError
Fields ErrorDescription ErrorTable
Record 1 System Resource Exceeded MsysAccessStorage
Record 2 System Resource Exceeded MsysRelationships
I deleted that table i.e. MsysCompactError and compacted MDB, after compact the table was
re-created.
#2 - Decompile the MDB
#3 - Moved the MDB on another PC and tried all things I knew but no luck.
I picked two or three days old back up set and applied all things above still the problem exists.
In short, I am not able to figure out if it is something wrong with Linked Tables OR the machine OR
the MDB itself.
Ozair.
---In MS_Access_Professionals@yahoogroups.com, <gary.schwartz@...> wrote:
Bloating is normal if you are actively changing structure in the database,
or the linked or local content changes a lot.
A warning: if the bloat gets too big, approaching 2G, the Access database
can get corrupted. While it is possible to recover it, there is
considerable effort and risk of failure involved.
While you can manually run "compact and repair" as you indicated, you could
also go to "Tools, Options" and select the "General" tab. On there you can
select "Compact on close". This will mean increased time each time you
close the file, but no worries about bloating.
If your back end is also Access, same applies there. SQL backend has other
ways to accomplish this.
Gary
Original email:
-----------------
From: ozairkhalid@...
Date: 11 Nov 2013 22:01:56 -0800
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] MS Access 2003 bloating excessively
Hi,
My front end MDB file is bloating excessively ( specially) when re-linking
tables using Linked Table Manager.
After compacting, the normal size of the front end MDB is 100MB which goes
up to 1GB ( even more ) during the re-link.
Any idea how to prevent it?
OS : Windows 2008 R2 64Bit
Database : SQL Server 2012
Office : MS Office 2003 with SP3 ( including Hotfix for SP3)
Ozair
--------------------------------------------------------------------
mail2web.com – Enhanced email for the mobile individual based on Microsoft®
Exchange - http://link.mail2web.com/Personal/EnhancedEmail
--
Sent from my Android phone with K-9 Mail.
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (16) |
Tidak ada komentar:
Posting Komentar