Results 1 to 6 of 6
  1. #1
    2 Star Lounger
    Join Date
    May 2002
    Location
    Dubai, UAE, United Arab Emirates
    Posts
    105
    Thanks
    0
    Thanked 0 Times in 0 Posts

    A2k Report Crashes AccessXP (XP SP1)

    G'day All.

    An old client of mine (Shaun) has just approached me with a problem with a database I wrote for A2k 2 years ago. The job I did involved three separate databases, the simplest of which (called the client version) was for Shaun's clients use, and revolved around one import form, one table and one report.

    Well Shaun was demonstrating the Client version recently, entered a few records then clicked preview, and Access immediately closed and he was back in windows. When he re-ran it, while his records were there, the various list boxes on the main form for searching through the records and entering items did not display the lists based on the records entered as they should. So he sent me a copy and asked me what was going on.

    Well I tried to run the file he sent me (mde) and it was as he described. Enter a few records - listboxes were not updated. Click preview button - Access closes straight away.

    I went back to my master copy of the mdb file. Ran it and immedately found a broken reference to MS Common Dialog controls (that shouldn't have been there anyway) and the DAO reference too far down the list. Fixed. So the list boxes update and the records can be entered and updated as normal. (I know this is dragging on ...)

    But now I'm left with the report. The database is (necessarily) in 2000 format. As soon as I preview/design the report, Access XP closes out straight away. Tried importing the report into a new database - report comes in OK, try to design - bang out again. Tried Compact and Repair. No errors - No fix either. Tried converting the mdb to XP format - No Good.

    I would rather not have to try and build the report again. My next step is to re-install VMWare and setup a Win2k install with Office 2000 and see if the report produces the same error in the version of the software I originally wrote it in. That will take a while.

    I know the report worked under A2k when I last looked at it !

    Anyone got any ideas ?

    Regards Ken.
    <img src=/S/confused.gif border=0 alt=confused width=15 height=20>

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: A2k Report Crashes AccessXP (XP SP1)

    Are you saying you can't even view the report in design mode? Can you see its code module in the VBE?

    One thing to try if you can see the module is to export it to a text file, then remove the code from the module. I don't recall whether AXP will let you remove an object module from the project explorer or not, but if it will, to it. Then see if you can open the report in design view. If you can, save the report with the HasModule property set to no. Then open it again in design view, go to the VBE and import the text file into the report's module. You can clear up some pretty weird corruption that way.
    Charlotte

  3. #3
    2 Star Lounger
    Join Date
    May 2002
    Location
    Dubai, UAE, United Arab Emirates
    Posts
    105
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A2k Report Crashes AccessXP (XP SP1)

    G'day Charlotte
    Curioser and Curioser. I open the database and edit a module. Then I click into the report module, which has one simple procedure. As soon as I take any editing action, Access quites out completely. If you like I could send you a copy of the database. It's quite simple and is about 280K zipped.
    I'm about to install Access 2000 into my Virtual Win2k. Standby!
    Regards ken.
    P.S. No, I can't open the report in Design Mode.

  4. #4
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: A2k Report Crashes AccessXP (XP SP1)

    I presume you have done a compact and repair to no avail. If so, then it sounds as if your report is hopelessly corrupted. I've not seen this in the 2000 format, but we did see it a time or two in 97, and ended up having to rebuild the form (in our case) from scratch to get things right again. For that reason we usually try to keep an archive copy of each project we work on so we can simply copy objects from it to the customer version if the wheels fall off. Sorry to not be more encouraging.
    Wendell

  5. #5
    2 Star Lounger
    Join Date
    May 2002
    Location
    Dubai, UAE, United Arab Emirates
    Posts
    105
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: A2k Report Crashes AccessXP (XP SP1)

    G'day Wendell

    Thanks for the reply. Yeah, Compact and Repair, and import by component and upgrade to XP format too. The thing is that the report and indeed the entire database operates perfectly under Access 2000. It's only when I run it under Access XP (in 2000 format, or after I convert it) that it behaves strangely.

    And yes I have several stages of backup copies. I've yet to go back through them and see whether they all crash, but that's a good idea - I'll do so.

    Regards Ken.

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,624
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: A2k Report Crashes AccessXP (XP SP1)

    One other idea - if you aren't using any A2K functionality, you might try converting it back to 97, and then convert it from 97 to XP directly - you can still keep it in the 2000 format. I've seen a similar problem going the other way - a form would work perfectly in XP, but cause a crash in 2000. Doing the reverse conversoion solved it. <img src=/S/confused.gif border=0 alt=confused width=15 height=20> <img src=/S/crazy.gif border=0 alt=crazy width=15 height=15>
    Wendell

Posting Permissions

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