Results 1 to 5 of 5
  1. #1
    4 Star Lounger
    Join Date
    Jan 2002
    Location
    Brookings, South Dakota, USA
    Posts
    449
    Thanks
    0
    Thanked 0 Times in 0 Posts

    db corruption (A2k3) (pls excuse the length)

    Hi All,
    Please excuse the length of this post as I am much more confused about this deal than I normally am.
    I've got a db that I've been hitting pretty hard in design, etc, lately. A couple of days ago I started running into problems with my code disappearing, a couple of times quite a bit of re-writing had to be done (until I started copying and saving into notepad, that is). Yes I know that with this latest and greatest version of Access, the form will open in the background when you happen to be editting code in its module without having opened the form first and it kinda hangs around (I think the same thing happens with the older versions, but not even to this annoying extent). if you close the code window, anything you happen to add or edit in its module will disappear if you're not careful. Well, this was happening whenever I just happened to change to view the form itself, not closing it. Then a couple of reports would not close. Even when clicking on the X, Access would ask if I wanted to save the changes, I click Yes, and it would not close. Then a couple of forms would open, but not be visible. I know this because if you tried to re-name the form in the database window, the error of 'you cannot rename a form when it is open' would popup. Actually, this was intermitant as you could double-click on the form in the database window and it would open. If you looked at the design of the form first, then clicked on Form View, it would open and not be visible. It was an even bet if it would open or not when called from the code within another form. These are simple popup forms, modal set to no with a dialog border, nothing fancy.
    So after that I opened a new database window and imported everything from the old into the new. I started having problems with a completely different report. So I imported that report from the old db. It came into the new db as rptJimPerryMinnesota7%1. I'm not sure why I did it, but I then deleted that report almost immediately. Closed the database, reopened the database and double clicked on a module (this module was not a form module-and it doesn't matter which one as I tried multiple modules all with the same result). An error message popped up (Error0). It took me twenty-some times clicking OK before it finally disappeared and opened the module. I did not even use this report
    QUESTION 1: I do not use macros at all and which property sheet would it be referring to, considering I did not even use the report?

    OK, I then opened another new db, slowly imported everything into it. When I got to importing the reports, I came to a report I had just designed within the last couple of days and a new error popped up, error1. I clicked the OK, the offending report did_not import, but the import process continued and error2 popped up and I Clicked OK and error3 popped up and would not allow me to import the then current report being imported. error2 and error3 happened once more, with the import process continuing after error in each case, but again did_not import the offending report.
    The import process continued until I came to the report referenced in error4. I hadn't used that report in months, and of course it really was in the import source (the old) db.
    Now thinking that I had a "clean" db I closed/compacted it and reopened it. Double-clicked on a module and low and behold error0 popped up again, but this time referencing an above mentioned report that could not be imported.
    QUESTION 2: Where do I go from here?

    As an added bonus, I've just discovered that all my queries no longer have any joins and the fields are are labeled Like so: Expr4: ClientPKID. The back-end has all the relationships intact however. I have relinked the tables.
    Again, please excuse the length of this post, but this db is quite large (but it does have fe and be) and really do not want to rebuild the entire thing.
    Thank you and please do not hesitate to ask for any information you need.

    gdr
    Attached Images Attached Images
    <IMG SRC=http://www.wopr.com/w3tuserpics/gdrezek_sig.jpg>
    "Those who dance are considered insane by those who can't hear the music" - George Carlin

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: db corruption (A2k3) (pls excuse the length)

    You're not going to like my reply, but my impression from your description is that the database you're trying to import from is too much corrupted to be useful. Start from an uncorrupted backup copy is probably the best you can do. I know it's a pain, for even if you have regular backups, it's difficult to determine how far to go back to be sure you avoid the corruption. Still, it beats rebuilding from scratch.

    Since I don't have Access 2003 myself, I don't know how much this new version contributes to the problem; what I read about it in this forum doesn't make me eager to try.

    Note: I hope you do turn off the Track Name Autocorrect options in each and every database. It's a known source of corruption.

  3. #3
    4 Star Lounger
    Join Date
    Jan 2002
    Location
    Brookings, South Dakota, USA
    Posts
    449
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: db corruption (A2k3) (pls excuse the length)

    Hi Hans,
    Yes, thank goodness, I do have back-ups, but as you stated, just how far back to I need to go is a very serious question.
    The biggest pain I've experienced with A2k3 is the way the forms/reports open in the background. You edit code in a subform, switch to the form, try and open it and get "errored" saying that the subform cannot be opened as it is open in design mode and then the form opens with a huge white space where the subform should be. It's more than annoying and a real 'pita' (I think there needs to be a smiley for that one).
    I'm betting that this http://support.microsoft.com/default.aspx?...b;en-us;q231676 is the cause of the looking for my reports which are no longer there or have been renamed.
    Thanks again Hans. <img src=/S/bow.gif border=0 alt=bow width=15 height=15>
    <IMG SRC=http://www.wopr.com/w3tuserpics/gdrezek_sig.jpg>
    "Those who dance are considered insane by those who can't hear the music" - George Carlin

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: db corruption (A2k3) (pls excuse the length)

    The subform behavior you describe is already present in Access 2002 (and perhaps 2000, I skipped that.) I haven't found it particularly annoying.

  5. #5
    4 Star Lounger
    Join Date
    Jan 2002
    Location
    Brookings, South Dakota, USA
    Posts
    449
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: db corruption (A2k3) (pls excuse the length)

    It didn't seem to bother me in A2k2 either, but to me something has changed with A2k3. Maybe it's that it didn't seem as intrusive, or something. I don't know. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>

    Oh well, I'll learn to live with it as I did with A2k and it's wonderful jumping help files (at least in the copies we had here on campus).

    gdr
    <IMG SRC=http://www.wopr.com/w3tuserpics/gdrezek_sig.jpg>
    "Those who dance are considered insane by those who can't hear the music" - George Carlin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •