Welcome to SPN

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

Sign Up Now!

Access 2002 crashes

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

Tags:
  1. JK

    JK
    Expand Collapse
    Guest

    Hi everybody,

    Out of seemingly nowhere access starts crashing with a message "access
    encountered a problem an needs to be closed" (or words to this effect).
    "Compact and repair" does not solve the problem. Further, it does that on
    some "old" databases that been working fine previously.

    I read the thread of a similar problem here but it does not appear to apply
    to me, here some more details:

    - I work on a design Master - the replica is on my laptop as backup only
    (not used by anybody)

    - All are MDB files with uncompiled VBA codes and SQL Server Compatible
    syntax (ANSI 92)

    - All tables, queries, forms and codes were created in Access 2002 (SP3)

    - It crashes on 2 occasions
    (a) Immediately after or during save of code or a form design in that
    case I can normally go back in and continue working which is a
    nuisance
    only - no message is displayed.

    (b) On opening a form whether in form view or design view - which is
    persistent. There is no problem with other forms incl those that
    are based on the
    same table - the crash is with a message.

    - There have been no recent updates done to access recently.

    - No viruses or spy programs found

    - Computer is HP Pavilion (abt 9 month old) with 512MB RAM wit heaps of
    empty hard disk space

    - Windows XP home up to date

    Any idea?

    Regards/JK
     
  2. Loading...


  3. Arvin Meyer [MVP]

    Arvin Meyer [MVP]
    Expand Collapse
    Guest

    Replication was designed to replica data, not the objects. Occasionally
    crashing and corruption occur when used to replicate objects. If you haven't
    done so already, I suggest that you split the database. Import the front-end
    (code, queries, forms, reports) into a new clean empty database. Just
    replicate the back-end (data tables).
    --
    Arvin Meyer, MCP, MVP
    Microsoft Access
    Free Access downloads
    http://www.datastrat.com
    http://www.mvps.org/access

    "JK" <Nobody@Home.com> wrote in message
    news:%233O%23avUrGHA.2464@TK2MSFTNGP03.phx.gbl...
    > Hi everybody,
    >
    > Out of seemingly nowhere access starts crashing with a message "access
    > encountered a problem an needs to be closed" (or words to this effect).
    > "Compact and repair" does not solve the problem. Further, it does that on
    > some "old" databases that been working fine previously.
    >
    > I read the thread of a similar problem here but it does not appear to
    > apply
    > to me, here some more details:
    >
    > - I work on a design Master - the replica is on my laptop as backup only
    > (not used by anybody)
    >
    > - All are MDB files with uncompiled VBA codes and SQL Server Compatible
    > syntax (ANSI 92)
    >
    > - All tables, queries, forms and codes were created in Access 2002 (SP3)
    >
    > - It crashes on 2 occasions
    > (a) Immediately after or during save of code or a form design in that
    > case I can normally go back in and continue working which is a
    > nuisance
    > only - no message is displayed.
    >
    > (b) On opening a form whether in form view or design view - which is
    > persistent. There is no problem with other forms incl those that
    > are based on the
    > same table - the crash is with a message.
    >
    > - There have been no recent updates done to access recently.
    >
    > - No viruses or spy programs found
    >
    > - Computer is HP Pavilion (abt 9 month old) with 512MB RAM wit heaps of
    > empty hard disk space
    >
    > - Windows XP home up to date
    >
    > Any idea?
    >
    > Regards/JK
    >
    >
     
  4. JK

    JK
    Expand Collapse
    Guest

    Thanks Arvin,

    Let me see I understand, do you mean that tables in the new database will
    be linked to the ones in the old database?

    If so, I can certainly do this, no problem with existing databases but with
    those that are still "work in progress" I can see difficulties as I still
    create and modify tables meaning that I have to switch databases in order to
    maintain table.

    I guess that it is a matter of "put up or shut up"

    Regards/JK



    "Arvin Meyer [MVP]" <a@m.com> wrote in message
    news:OUeS1VZrGHA.3828@TK2MSFTNGP03.phx.gbl...
    > Replication was designed to replica data, not the objects. Occasionally
    > crashing and corruption occur when used to replicate objects. If you
    > haven't done so already, I suggest that you split the database. Import the
    > front-end (code, queries, forms, reports) into a new clean empty database.
    > Just replicate the back-end (data tables).
    > --
    > Arvin Meyer, MCP, MVP
    > Microsoft Access
    > Free Access downloads
    > http://www.datastrat.com
    > http://www.mvps.org/access
    >
    > "JK" <Nobody@Home.com> wrote in message
    > news:%233O%23avUrGHA.2464@TK2MSFTNGP03.phx.gbl...
    >> Hi everybody,
    >>
    >> Out of seemingly nowhere access starts crashing with a message "access
    >> encountered a problem an needs to be closed" (or words to this effect).
    >> "Compact and repair" does not solve the problem. Further, it does that on
    >> some "old" databases that been working fine previously.
    >>
    >> I read the thread of a similar problem here but it does not appear to
    >> apply
    >> to me, here some more details:
    >>
    >> - I work on a design Master - the replica is on my laptop as backup only
    >> (not used by anybody)
    >>
    >> - All are MDB files with uncompiled VBA codes and SQL Server Compatible
    >> syntax (ANSI 92)
    >>
    >> - All tables, queries, forms and codes were created in Access 2002 (SP3)
    >>
    >> - It crashes on 2 occasions
    >> (a) Immediately after or during save of code or a form design in that
    >> case I can normally go back in and continue working which is a
    >> nuisance
    >> only - no message is displayed.
    >>
    >> (b) On opening a form whether in form view or design view - which is
    >> persistent. There is no problem with other forms incl those that
    >> are based on the
    >> same table - the crash is with a message.
    >>
    >> - There have been no recent updates done to access recently.
    >>
    >> - No viruses or spy programs found
    >>
    >> - Computer is HP Pavilion (abt 9 month old) with 512MB RAM wit heaps of
    >> empty hard disk space
    >>
    >> - Windows XP home up to date
    >>
    >> Any idea?
    >>
    >> Regards/JK
    >>
    >>

    >
    >
     
  5. Arvin Meyer [MVP]

    Arvin Meyer [MVP]
    Expand Collapse
    Guest

    "JK" <Nobody@Home.com> wrote in message
    news:uBpLJAdrGHA.4408@TK2MSFTNGP02.phx.gbl...
    > Thanks Arvin,
    >
    > Let me see I understand, do you mean that tables in the new database will
    > be linked to the ones in the old database?


    Yes, as soon as you are sure that the links are working, delete all the
    objects (code, queries, forms, reports) from the old database and either
    create a new replica (preferred) or sync up with your existing one.

    > If so, I can certainly do this, no problem with existing databases but
    > with
    > those that are still "work in progress" I can see difficulties as I still
    > create and modify tables meaning that I have to switch databases in order
    > to
    > maintain table.


    I just click on the links from the FileOpen menu. BTW, if you have several
    databases, it's a good idea to go to Tools ... Options ... General tab and
    change the Recently Used Databases count from 4 to 9.
    --
    Arvin Meyer, MCP, MVP
    Microsoft Access
    Free Access downloads
    http://www.datastrat.com
    http://www.mvps.org/access
     

Share This Page