Converting the BE is not necessary. Nothing in the Data gets
changed or converted when converting from 2000 to 2003.
Converting changes the VBA project, which converts the
Forms and Reports. Unless you have Forms or Reports
in the BE, converting the BE only converts the version number.
Converting the version number from Access 2000 to Access
2003 may prevent you from opening the BE in Access 2000.
But unless you have forms or reports, it's just the version
number. If the old project was empty, the new project is
empty too.
'Converting' a BE does a compact and repair on the BE.
After you have done a compact and repair on the BE,
you may need to re-link the FE, or at least compact and
repair the FE.
This is sometimes required if you have made changes to
the BE at some stage, and have not compacted since.
Converting the FE before compacting the BE does NOT
avoid this potential problem. Sometimes you need to
relink or compact the FE AFTER compacting the BE.
So if you plan to 'convert' the BE, and have not been
compacting the BE, you should be aware that you may
need to relink, or at least compact, the FE
(david)
"sweeneysmsm" <(E-Mail Removed)> wrote in message
news:459F50C3-B6D2-4781-B6B4-(E-Mail Removed)...
>I have an Access database installed on a network. The database is unsecured
> since the information is not such that it needs to be. The database is
> split
> with front-ends available to the accessing individuals and the Back-end
> having linked tables.
>
> Everything is fine. Their database format is Access 2000 but they are
> using
> Access 2003. How do I go about upgrading them to 2003 using the Convert
> Database Utility, bearing in mind that I have front-ends and back-end?
>
> Thanks for any insight. Wasn't quite sure where this question should go in
> the Forum so tell me if I made the wrong guess.
>
> Mary
>
|