Re: Convert XP to 2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Brendan:

Sorry for not responding sooner, but I've been busy on some other projects.
Thank you very much for the info. I checked the Smart Access article. It's
been very helpful. I'll try the keyword suggestions as well.

Thanks again!
--
Paul


"Brendan Reynolds" wrote:

> Access 2003 didn't introduce any new file format, so there isn't really any
> 'conversion' for anyone to write about. There is certainly plenty to be said
> on the subject of 'macro' security, code signing and digital certificates,
> however. Try using those keywords instead, and you'll get plenty of hits -
> here's a link to some search results using these keywords - the Smart Access
> article is a good starting point for an over-view of the issues. Also check
> out the Google newsgroup archives for lots of posts on this issue.
>
> http://search.microsoft.com/search/results.aspx?qu=access+macro+security+digital+signature
>
> --
> Brendan Reynolds (MVP)
>
> "PaulJS" <PaulJS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:D1F4A40C-19B8-41BE-8197-CB34E7309BFA@xxxxxxxxxxxxxxxx
> > Hi,
> > We're running an Access 2002 front end (SQL Server back end). The parent
> > company is migrating to 2003 and I've run some tests on converting the
> > 2002
> > front end to 2003. When I start the converted database, I get security
> > warnings on the VBA code that runs in the startup form. (The code is just
> > setting a few text box values with dates and company info.) I've been
> > searching MSDN and TechNet for articles on migrating to 2003, but have
> > been
> > unable to find anything that contains guidelines for converting from 2002
> > to
> > 2003.
> >
> > I was hoping to get some help on where I can find some info, perhaps on
> > the
> > Microsoft web site, that details the changes in 2003 that developers need
> > to
> > be aware of, especially with security issues. Any help would be
> > appreciated!
> > --
> > PaulJS
>
>
>
.