Troubles with Converting dbs to Access Database Project?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ivan - 16 Apr 2005 00:21 GMT

I am in the process of brushing up my web site. Are there any specific
things I should do or perform prior to attempting to convert the design to
ADP?

If I have a combo box for 6000+ customers, will that slow the process and
freeze up the program?

Thanks,
Ivan.

Reply to this Message

Brendan Reynolds - 16 Apr 2005 11:27 GMT

An ADP has nothing to do with web sites, Ivan. An ADP is a front-end,
application file that runs on the desktop and doesn't contain any data. Did
you mean that you wanted to convert your web pages to DAPs (Data Access
Pages)? Or perhaps you mean you're moving your data from a Jet database
(MDB) to SQL Server?

Signature

Brendan Reynolds (MVP)

>I am in the process of brushing up my web site. Are there any specific
> things I should do or perform prior to attempting to convert the design to
[quoted text clipped - 5 lines]
> Thanks,
> Ivan.

Reply to this Message

Ivan - 16 Apr 2005 22:47 GMT

I truly apologize for making such a stupd typo. It was a long day when I
posted my question.
I put together a mdb access database on my laptop which I would like to
convert to access database project (that access 2003 offers as a tool). It's
tables will be stored on a SQL 2000 server. The existing order entry web
site will be linked to the tables. I will NOT be putting together any DAP's.

I have never done a conversion. Once I have the mdb fully functional and
tested, I would like to make it into an ADP.

THANK YOU VERY Much!
Ivan.

> An ADP has nothing to do with web sites, Ivan. An ADP is a front-end,
> application file that runs on the desktop and doesn't contain any data. Did
[quoted text clipped - 10 lines]
> > Thanks,
> > Ivan.

Reply to this Message

Brendan Reynolds - 17 Apr 2005 12:57 GMT

Hi Ivan,

I'm still a little confused, because as I said earlier, ADPs don't have
anything to do with web apps. Perhaps you mean that you have both a web app
and a desktop Access app using the same data?

Anyway, I would certainly *not* recommend making an MDB app "fully
functional and tested" and *then* converting to ADP, because you will need
to make a lot of changes to the app when you convert it. Lot's of things
that work in an MDB app don't work in an ADP. Why spend time perfecting and
testing something that's going to change anyway?

Signature

Brendan Reynolds (MVP)

>I truly apologize for making such a stupd typo. It was a long day when I
> posted my question.
[quoted text clipped - 28 lines]
>> > Thanks,
>> > Ivan.

Reply to this Message

david epsom dot com dot au - 18 Apr 2005 08:04 GMT

There is a tool in Access 2003 that converts an MDB
project to an ADP? Where?

(david)

>I truly apologize for making such a stupd typo. It was a long day when I
> posted my question.
[quoted text clipped - 28 lines]
>> > Thanks,
>> > Ivan.

Reply to this Message

Brendan Reynolds - 18 Apr 2005 09:40 GMT

It's one of the options in the Upsizing Wizard, David. On about the fifth
page of the wizard, you get the option 'Create a new Access client/server
application', which creates an ADP.

In my (admittedly limited) experience, I have not found it to work very well
with a non-trivial MDB application.

Signature

Brendan Reynolds (MVP)

> There is a tool in Access 2003 that converts an MDB
> project to an ADP? Where?
[quoted text clipped - 33 lines]
>>> > Thanks,
>>> > Ivan.

Reply to this Message

Ivan - 18 Apr 2005 20:21 GMT

Thank you very much Brendan. You are correct. Our website will use and
store data in the tables of the project. Now that I know that the conversion
will require changes, I will convert and then brush up.

> I am in the process of brushing up my web site. Are there any specific
> things I should do or perform prior to attempting to convert the design to
[quoted text clipped - 5 lines]
> Thanks,
> Ivan.

Reply to this Message