Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Access 2003 Serious Errors, Really need some help

Discussion in 'Information Technology' started by Mr B, Jul 28, 2006.

  1. Mr B

    Mr B
    Expand Collapse
    Guest

    Hey, guys,

    Sorry for posting again on this same subject, but, although Jerry Whittle
    did reply and attempt to help, I am still perplexed by this issue and I
    really need some help with this one.

    I posted about this issue earler today.

    I am experiencing complete shut down of Access under certain conditions.
    These shut downs are occurring even when I just create a new database, create
    a new form, create one button that just changes the Caption of a label when
    the button is clicked.

    When the problem occurs, I get the "Micorsoft Office Access" dialog box that
    says,"Microsoft Office Access has encountered a problem and needs to close.
    We are sorry for the inconvience." One option to Compact and Repair the
    database. Button to Send error to Microsoft, etc. Required to Exit.

    If I open the form in design mode, then just click the "Code" button from
    the menu, I get the error.

    If I first click on the From selection button at the top left corner of the
    form and then click the "Code" button I get the error.

    If i click on a section of the form or a control on the form and then clilck
    the "Code" button I do not get the error. However, if I then switch back to
    the database window and attempt to open a second form in design mode I get
    the error.

    I have tried many things including: updating Windows and Office; compacting
    and reparing the database; importing all objects into a new database file;
    starting with an empty database file and more. Nothing has helped.

    I have been able to determine that we have at least on machine on which this
    does not occur. I am beginning to think that it may be machine related, but I
    have absolutely no idea what to look for to try to correct the problem.

    I really need some help with this one.

    Mr B
     
  2. Loading...


  3. Sylvain Lafontaine

    Sylvain Lafontaine
    Expand Collapse
    Guest

    You can try installing or reinstalling the latest service packs for both JET
    4.0 and MDAC 8:

    MDAC 8 Sp1:

    http://www.microsoft.com/downloads/...95-EFC2-4F8E-A9E0-3A1AFBD5922E&displaylang=en

    Jet 4.0 SP8:

    http://www.microsoft.com/downloads/results.aspx?pocId=&freetext=jet&DisplayLang=enDownloading

    I don't know if this will help but obviously, the fact that you have trouble
    even with a newly created database is not a good sign.

    In your previous post, you say that you are linked to SQL-Server, is this a
    MDF file with linked tables or an ADP project? Has this server been patched
    with the latest service packs, too? Are you using a dbo account or some
    restricted user account?

    It's possible that some types of SQL-Server fields like Decimal might be the
    cause of your problem, too.

    --
    Sylvain Lafontaine, ing.
    MVP - Technologies Virtual-PC
    E-mail: http://cerbermail.com/?QugbLEWINF


    "Mr B" <MrB@discussions.microsoft.com> wrote in message
    news:696F8379-6DAE-438B-84C0-781208C06AB9@microsoft.com...
    > Hey, guys,
    >
    > Sorry for posting again on this same subject, but, although Jerry Whittle
    > did reply and attempt to help, I am still perplexed by this issue and I
    > really need some help with this one.
    >
    > I posted about this issue earler today.
    >
    > I am experiencing complete shut down of Access under certain conditions.
    > These shut downs are occurring even when I just create a new database,
    > create
    > a new form, create one button that just changes the Caption of a label
    > when
    > the button is clicked.
    >
    > When the problem occurs, I get the "Micorsoft Office Access" dialog box
    > that
    > says,"Microsoft Office Access has encountered a problem and needs to
    > close.
    > We are sorry for the inconvience." One option to Compact and Repair the
    > database. Button to Send error to Microsoft, etc. Required to Exit.
    >
    > If I open the form in design mode, then just click the "Code" button from
    > the menu, I get the error.
    >
    > If I first click on the From selection button at the top left corner of
    > the
    > form and then click the "Code" button I get the error.
    >
    > If i click on a section of the form or a control on the form and then
    > clilck
    > the "Code" button I do not get the error. However, if I then switch back
    > to
    > the database window and attempt to open a second form in design mode I get
    > the error.
    >
    > I have tried many things including: updating Windows and Office;
    > compacting
    > and reparing the database; importing all objects into a new database file;
    > starting with an empty database file and more. Nothing has helped.
    >
    > I have been able to determine that we have at least on machine on which
    > this
    > does not occur. I am beginning to think that it may be machine related,
    > but I
    > have absolutely no idea what to look for to try to correct the problem.
    >
    > I really need some help with this one.
    >
    > Mr B
     
  4. Mr B

    Mr B
    Expand Collapse
    Guest

    Sylvain,

    Thanks so much for the response. I will try your suggestions for
    reinstalling the latest service packs.

    As for the SQL Server part, I have, at least for the moment, basically
    rulled out any issues with the database or the link to it, as there does not
    seem to be any problem with retreiveing data and/or writing data. Table
    opening and closing does not create any problems.

    I am thinking that there has to be some problem with something that is
    conflicting with the VBA part of Access. I have not had enough experience
    with Access 2003 yet to know if there are any special issues. I have worked
    bunches in all other versions since 2.0 but have never had an issue like this
    one.

    I will get back to you when I have tried reinstalling the service packs.

    Mr B


    "Sylvain Lafontaine" wrote:

    > You can try installing or reinstalling the latest service packs for both JET
    > 4.0 and MDAC 8:
    >
    > MDAC 8 Sp1:
    >
    > http://www.microsoft.com/downloads/...95-EFC2-4F8E-A9E0-3A1AFBD5922E&displaylang=en
    >
    > Jet 4.0 SP8:
    >
    > http://www.microsoft.com/downloads/results.aspx?pocId=&freetext=jet&DisplayLang=enDownloading
    >
    > I don't know if this will help but obviously, the fact that you have trouble
    > even with a newly created database is not a good sign.
    >
    > In your previous post, you say that you are linked to SQL-Server, is this a
    > MDF file with linked tables or an ADP project? Has this server been patched
    > with the latest service packs, too? Are you using a dbo account or some
    > restricted user account?
    >
    > It's possible that some types of SQL-Server fields like Decimal might be the
    > cause of your problem, too.
    >
    > --
    > Sylvain Lafontaine, ing.
    > MVP - Technologies Virtual-PC
    > E-mail: http://cerbermail.com/?QugbLEWINF
    >
    >
    > "Mr B" <MrB@discussions.microsoft.com> wrote in message
    > news:696F8379-6DAE-438B-84C0-781208C06AB9@microsoft.com...
    > > Hey, guys,
    > >
    > > Sorry for posting again on this same subject, but, although Jerry Whittle
    > > did reply and attempt to help, I am still perplexed by this issue and I
    > > really need some help with this one.
    > >
    > > I posted about this issue earler today.
    > >
    > > I am experiencing complete shut down of Access under certain conditions.
    > > These shut downs are occurring even when I just create a new database,
    > > create
    > > a new form, create one button that just changes the Caption of a label
    > > when
    > > the button is clicked.
    > >
    > > When the problem occurs, I get the "Micorsoft Office Access" dialog box
    > > that
    > > says,"Microsoft Office Access has encountered a problem and needs to
    > > close.
    > > We are sorry for the inconvience." One option to Compact and Repair the
    > > database. Button to Send error to Microsoft, etc. Required to Exit.
    > >
    > > If I open the form in design mode, then just click the "Code" button from
    > > the menu, I get the error.
    > >
    > > If I first click on the From selection button at the top left corner of
    > > the
    > > form and then click the "Code" button I get the error.
    > >
    > > If i click on a section of the form or a control on the form and then
    > > clilck
    > > the "Code" button I do not get the error. However, if I then switch back
    > > to
    > > the database window and attempt to open a second form in design mode I get
    > > the error.
    > >
    > > I have tried many things including: updating Windows and Office;
    > > compacting
    > > and reparing the database; importing all objects into a new database file;
    > > starting with an empty database file and more. Nothing has helped.
    > >
    > > I have been able to determine that we have at least on machine on which
    > > this
    > > does not occur. I am beginning to think that it may be machine related,
    > > but I
    > > have absolutely no idea what to look for to try to correct the problem.
    > >
    > > I really need some help with this one.
    > >
    > > Mr B

    >
    >
    >
     
  5. Sylvain Lafontaine

    Sylvain Lafontaine
    Expand Collapse
    Guest

    Another possibility would be some change to the security levels of the
    database system tables. Is the account used a dbo account or something
    else?

    --
    Sylvain Lafontaine, ing.
    MVP - Technologies Virtual-PC
    E-mail: http://cerbermail.com/?QugbLEWINF


    "Mr B" <MrB@discussions.microsoft.com> wrote in message
    news:F4C2D4BC-931A-4D50-95DB-C616205A0A04@microsoft.com...
    > Sylvain,
    >
    > Thanks so much for the response. I will try your suggestions for
    > reinstalling the latest service packs.
    >
    > As for the SQL Server part, I have, at least for the moment, basically
    > rulled out any issues with the database or the link to it, as there does
    > not
    > seem to be any problem with retreiveing data and/or writing data. Table
    > opening and closing does not create any problems.
    >
    > I am thinking that there has to be some problem with something that is
    > conflicting with the VBA part of Access. I have not had enough experience
    > with Access 2003 yet to know if there are any special issues. I have
    > worked
    > bunches in all other versions since 2.0 but have never had an issue like
    > this
    > one.
    >
    > I will get back to you when I have tried reinstalling the service packs.
    >
    > Mr B
    >
    >
    > "Sylvain Lafontaine" wrote:
    >
    >> You can try installing or reinstalling the latest service packs for both
    >> JET
    >> 4.0 and MDAC 8:
    >>
    >> MDAC 8 Sp1:
    >>
    >> http://www.microsoft.com/downloads/...95-EFC2-4F8E-A9E0-3A1AFBD5922E&displaylang=en
    >>
    >> Jet 4.0 SP8:
    >>
    >> http://www.microsoft.com/downloads/results.aspx?pocId=&freetext=jet&DisplayLang=enDownloading
    >>
    >> I don't know if this will help but obviously, the fact that you have
    >> trouble
    >> even with a newly created database is not a good sign.
    >>
    >> In your previous post, you say that you are linked to SQL-Server, is this
    >> a
    >> MDF file with linked tables or an ADP project? Has this server been
    >> patched
    >> with the latest service packs, too? Are you using a dbo account or some
    >> restricted user account?
    >>
    >> It's possible that some types of SQL-Server fields like Decimal might be
    >> the
    >> cause of your problem, too.
    >>
    >> --
    >> Sylvain Lafontaine, ing.
    >> MVP - Technologies Virtual-PC
    >> E-mail: http://cerbermail.com/?QugbLEWINF
    >>
    >>
    >> "Mr B" <MrB@discussions.microsoft.com> wrote in message
    >> news:696F8379-6DAE-438B-84C0-781208C06AB9@microsoft.com...
    >> > Hey, guys,
    >> >
    >> > Sorry for posting again on this same subject, but, although Jerry
    >> > Whittle
    >> > did reply and attempt to help, I am still perplexed by this issue and I
    >> > really need some help with this one.
    >> >
    >> > I posted about this issue earler today.
    >> >
    >> > I am experiencing complete shut down of Access under certain
    >> > conditions.
    >> > These shut downs are occurring even when I just create a new database,
    >> > create
    >> > a new form, create one button that just changes the Caption of a label
    >> > when
    >> > the button is clicked.
    >> >
    >> > When the problem occurs, I get the "Micorsoft Office Access" dialog box
    >> > that
    >> > says,"Microsoft Office Access has encountered a problem and needs to
    >> > close.
    >> > We are sorry for the inconvience." One option to Compact and Repair
    >> > the
    >> > database. Button to Send error to Microsoft, etc. Required to Exit.
    >> >
    >> > If I open the form in design mode, then just click the "Code" button
    >> > from
    >> > the menu, I get the error.
    >> >
    >> > If I first click on the From selection button at the top left corner of
    >> > the
    >> > form and then click the "Code" button I get the error.
    >> >
    >> > If i click on a section of the form or a control on the form and then
    >> > clilck
    >> > the "Code" button I do not get the error. However, if I then switch
    >> > back
    >> > to
    >> > the database window and attempt to open a second form in design mode I
    >> > get
    >> > the error.
    >> >
    >> > I have tried many things including: updating Windows and Office;
    >> > compacting
    >> > and reparing the database; importing all objects into a new database
    >> > file;
    >> > starting with an empty database file and more. Nothing has helped.
    >> >
    >> > I have been able to determine that we have at least on machine on which
    >> > this
    >> > does not occur. I am beginning to think that it may be machine related,
    >> > but I
    >> > have absolutely no idea what to look for to try to correct the problem.
    >> >
    >> > I really need some help with this one.
    >> >
    >> > Mr B

    >>
    >>
    >>
     

Share This Page