Welcome to SPN

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

Sign Up Now!

upgrade from ACCESS 2000 to 2003

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

Tags:
  1. Hugh Welford

    Hugh Welford
    Expand Collapse
    Guest

    Hi,
    I am having to upgrade a substantial db application from ACCESS 2000 to 2003

    Are there any known issues in this exercise which I should know about and
    clue up on before starting on it?

    Presume re-compilation will be necessary.

    Thanks
    Hugh
     
  2. Loading...

    Similar Threads Forum Date
    Sikh News Punjab plans to upgrade infra in steel city (Express India) Breaking News Sep 22, 2008
    Sikh News Punjab to upgrade security training institute (New Kerala) Breaking News Mar 21, 2008
    Sikh News Punjab to upgrade veterinary hospital, poly clinics (New Kerala) Breaking News Jan 24, 2008
    Sikh News Rs 141 crore plan to upgrade schools in Punjab (Deepika) Breaking News Dec 29, 2007
    Sikh News Punjab approves projects to upgrade power transmission (Indian Express Finance vi Breaking News Dec 7, 2007

  3. Allen Browne

    Allen Browne
    Expand Collapse
    Guest

    Access 2003 can use an A2000 format database directly. There is no need to
    convert to the A2002/03 format unless you want to release an MDE.

    Strictly, a recompile should not be necessary going that direction, though I
    would recommend it if you modify the code in A2003, and then want to run it
    in A2000.

    If you suddenly find that A2003 is crashing when you load a form that has a
    subform that is based on a query, there is a bug relating to the
    LinkChildFields referring directly to an AccessField object (i.e. not to a
    control in the subform.)

    A2003 can reject a reference such as:
    Forms!Form1!Sub1!Text0
    which is solved if you use the Form property to refer to the form in the
    subform control, i.e.:
    Forms!Form1!Sub1.Form!Text0

    A2003 can have problems with recognising network printers that work fine in
    other programs and earlier versions.

    The Themed Controls in A2003 can cause problems with transparency on tab
    controls, triple-state check boxes that are not visually distinct, and
    flickering of labels that are not directly on the form. More info:
    http://allenbrowne.com/ser-46.html

    You are probably aware of the crazy security warnings that A2003 gives,
    advising you not to use your own database, ... up to 3 times, ... every time
    you open it. You will want to dump those by setting macro security to low:
    Tools | Options | Macro | Security.

    Presumably you are also aware or the impact of other references. These will
    need adjusting manually if you referenced the calendar control, MS Graph,
    other ActiveX controls, or an Office library such as Excel 9.0. You may also
    need to disambiguate things like the Recordset object. More info:
    http://allenbrowne.com/ser-38.html

    --
    Allen Browne - Microsoft MVP. Perth, Western Australia.
    Tips for Access users - http://allenbrowne.com/tips.html
    Reply to group, rather than allenbrowne at mvps dot org.

    "Hugh Welford" <hugh.welford@btinternet.com> wrote in message
    news:OFrz5m%23gGHA.4368@TK2MSFTNGP03.phx.gbl...
    > Hi,
    > I am having to upgrade a substantial db application from ACCESS 2000 to
    > 2003
    >
    > Are there any known issues in this exercise which I should know about and
    > clue up on before starting on it?
    >
    > Presume re-compilation will be necessary.
    >
    > Thanks
    > Hugh
     
  4. hugh welford

    hugh welford
    Expand Collapse
    Guest

    Thanks Allen


    "Allen Browne" <AllenBrowne@SeeSig.Invalid> wrote in message
    news:eykOAv%23gGHA.3376@TK2MSFTNGP03.phx.gbl...
    > Access 2003 can use an A2000 format database directly. There is no need to
    > convert to the A2002/03 format unless you want to release an MDE.
    >
    > Strictly, a recompile should not be necessary going that direction, though
    > I would recommend it if you modify the code in A2003, and then want to run
    > it in A2000.
    >
    > If you suddenly find that A2003 is crashing when you load a form that has
    > a subform that is based on a query, there is a bug relating to the
    > LinkChildFields referring directly to an AccessField object (i.e. not to a
    > control in the subform.)
    >
    > A2003 can reject a reference such as:
    > Forms!Form1!Sub1!Text0
    > which is solved if you use the Form property to refer to the form in the
    > subform control, i.e.:
    > Forms!Form1!Sub1.Form!Text0
    >
    > A2003 can have problems with recognising network printers that work fine
    > in other programs and earlier versions.
    >
    > The Themed Controls in A2003 can cause problems with transparency on tab
    > controls, triple-state check boxes that are not visually distinct, and
    > flickering of labels that are not directly on the form. More info:
    > http://allenbrowne.com/ser-46.html
    >
    > You are probably aware of the crazy security warnings that A2003 gives,
    > advising you not to use your own database, ... up to 3 times, ... every
    > time you open it. You will want to dump those by setting macro security to
    > low:
    > Tools | Options | Macro | Security.
    >
    > Presumably you are also aware or the impact of other references. These
    > will need adjusting manually if you referenced the calendar control, MS
    > Graph, other ActiveX controls, or an Office library such as Excel 9.0. You
    > may also need to disambiguate things like the Recordset object. More info:
    > http://allenbrowne.com/ser-38.html
    >
    > --
    > Allen Browne - Microsoft MVP. Perth, Western Australia.
    > Tips for Access users - http://allenbrowne.com/tips.html
    > Reply to group, rather than allenbrowne at mvps dot org.
    >
    > "Hugh Welford" <hugh.welford@btinternet.com> wrote in message
    > news:OFrz5m%23gGHA.4368@TK2MSFTNGP03.phx.gbl...
    >> Hi,
    >> I am having to upgrade a substantial db application from ACCESS 2000 to
    >> 2003
    >>
    >> Are there any known issues in this exercise which I should know about
    >> and clue up on before starting on it?
    >>
    >> Presume re-compilation will be necessary.
    >>
    >> Thanks
    >> Hugh

    >
    >
     

Share This Page