Re: Access 2003 missing the intranet or the website

David W. Fenton <dXXXfenton@xxxxxxxxxxxxxxxx> wrote:
> "Br@dley" <n0mail@xxxxxx> wrote in
> news:qtVDe.54944$oJ.48077@xxxxxxxxxxxxxxxxxxxxxxxxxx:
>
>> I actually now remember an instance of converting a 97 db to 2000
>> and it somehow got a reference to some internet thing..... I never
>> converted after that. Always started with a clean db and imported.
>
> That seems a ludicrous response to an extremely unusual condition.
>
> I have *never* done an import of A97 into A2K -- I've always
> converted, and I've never encountered a single problem as a result.
>
> Most of my projects that are in production use with A2K are actually
> programmed in A97, so I do this literally 100s of times a year (if
> not 1,000s).

And yet MS offers this advice to ppl who can't convert their DB:


If you can't successfully convert your Microsoft Access file by pointing
to Database Utilities on the Tools menu and then clicking the Convert
Database/Project command, use the following procedure.

1.. In Access 2002 or later, click New on the File menu and create a
new Access database (Microsoft Access database: A collection of data and
objects (such as tables, queries, or forms) that is related to a
particular topic or purpose. The Microsoft Jet database engine manages
the data.) or Access project (Microsoft Access project: An Access file
that connects to a Microsoft SQL Server database and is used to create
client/server applications. A project file doesn't contain any data or
data-definition-based objects such as tables and views.).

2.. On the File menu, point to Get External Data and click Import.

3.. In the Import dialog box, select the Access file you want to
convert.

4.. In the Import Objects dialog box, select the database objects
(database objects: An Access database contains objects such as tables,
queries, forms, reports, pages, macros, and modules. An Access project
contains objects such as forms, reports, pages, macros, and modules.)
you want to import. If the new Access file is an Access project that you
have connected to a Microsoft SQL Server database, import only the
forms, reports, pages, macros, and modules.


--
regards,

Bradley

A Christian Response
http://www.pastornet.net.au/response


.

Relevant Pages

  • RE: toll bars
    ... You can import custom menus and toolbars from a Microsoft Access database ... (database: A collection of data related to a particular subject or purpose. ... Access project (Microsoft Access project: An Access file that connects to a ... Under Import, click Menus and Toolbars. ...
    (microsoft.public.access.externaldata)
  • Re: Access 2002 command line options.
    ... > database Opens the specified database. ... > /excl Opens the specified database for exclusive access. ... > /user user name Starts Microsoft Access using the specified user name. ... To compact to a different name, specify a target ...
    (microsoft.public.access.developers.toolkitode)
  • Re: Cant access code
    ... See http://www.QBuilt.com for all your database needs. ... See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials. ... Create a new database file and import all objects except the corrupt form. ... If you have a recent backup, import this form from the backup and check ...
    (microsoft.public.access.modulesdaovba)
  • Re: Communication Log
    ... Tony Toews, Microsoft Access MVP ... May I send you copy of the database that I made? ... Dropdown box (I can select a value to store in the ... The above controls are set up in a page using te tab control. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)