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?
--
Brendan Reynolds (MVP)
"Ivan" <(E-Mail Removed)> wrote in message
news:849C51FA-510A-47E3-A19C-(E-Mail Removed)...
>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.
>
> "Brendan Reynolds" wrote:
>
>> 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?
>> --
>> Brendan Reynolds (MVP)
>>
>> "Ivan" <(E-Mail Removed)> wrote in message
>> news:2056C378-2DC4-46CF-87CA-(E-Mail Removed)...
>> >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.
>>
>>
>>
|