Re: Converting Access 97 to Access 2002

• Previous message: Steve Huff: "Re: A problem difficulty for me but easy for you!"
• Messages sorted by: [ date ] [ thread ]

Date: Sun, 2 Jan 2005 07:13:30 +0800

"Allen Browne" <AllenBrowne@SeeSig.Invalid> ¼¶¼g©ó¶l¥ó·s»D
:u$YES4UwEHA.3164@TK2MSFTNGP10.phx.gbl...
> See:
> Converting from Access 97 to 2000, 2002 or 2003
> at:
> http://members.iinet.net.au/~allenbrowne/ser-48.html
>
> Particularly:
> - Make sure this workstation has the correct service packs (esp. JET).
>
> - Verify the references are okay.
>
> - Double-check that Name AutoCorrect is off (Usability #1).
>
> - Read the bit about crashes (Usability #2).
>
> If you think you have an issue with temp objects and resources, it would
be
> a good idea to create an MDE for the users. An MDE can't decompile, and
> won't let them fiddle with design changes.
>
> --
> 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.
>
> "J. Toews" <JToews@discussions.microsoft.com> wrote in message
> news:D78A2C63-31CA-4E79-AA49-20114EEE3636@microsoft.com...
> > We recently converted to Access 2002 from 97 and NT to XP. One of the
> > databases we converted keeps corrupting when printing reports from the
> > user
> > interface (split DB). This interface is used by just one person. The
> > database in question is relatively simple, not much custom VBA code in
it.
> > All forms and code were built using the Access wizards - e.g. User form
> > with
> > a Open Report command button, Close Form button all simple stuff.
> >
> > I know this is a really general question that might be impossible for
> > someone who isn't standing behind me to answer but is anyone else
> > experiencing the same type of problems with Access DB's after converting
> > to a
> > newer version.
> >
> > The only possible explanations we have for this is either their is
> > something
> > wrong with the user's workstation or Access is creating too many
temporary
> > form/report objects when opening reports draining their system
resources.
> > The
> > weird thing about this is when we test the app. on other workstations we
> > seem
> > to have no problems.
> >
> > Any ideas that would point us in the right direction would be greatly
> > appreciated!
> >
> > Thanks in advance.
>
>

• Previous message: Steve Huff: "Re: A problem difficulty for me but easy for you!"
• Messages sorted by: [ date ] [ thread ]