Please help me quick start on DAP:

1 - Will DAP let me put up my existing Forms on the net?

2 - What about forms with 'Tabs' ?

2.5 - Must we create the DAP pages while working directly on the back
end or can we do it all via the Front End?

3 - Are there issues with Forms & Queries that are built on several
tables?

4 - Will DAP let you update more than one table at a time?
(Example: Looking at a Form built on tblAccount and tblContacts... can
you change or add data to both from a single form/screen??)

5 - Looks like we would have to require our field sales people to use
MS Internet Explorer to be sure DAP would work... right?

6 - What issues may we run into using DAP to make our data base
accessable to a field sales force on the net?

7 - Is it a major project to take an existing dB and put it on the net
using DAP?

Thanks for any help in jump starting me on this.

Mel

Mel wrote:
> Please help me quick start on DAP:
>
> 1 - Will DAP let me put up my existing Forms on the net?
>
> 2 - What about forms with 'Tabs' ?
>
> 2.5 - Must we create the DAP pages while working directly on the back
> end or can we do it all via the Front End?
>
> 3 - Are there issues with Forms & Queries that are built on several
> tables?
>
> 4 - Will DAP let you update more than one table at a time?
> (Example: Looking at a Form built on tblAccount and tblContacts... can
> you change or add data to both from a single form/screen??)
>
> 5 - Looks like we would have to require our field sales people to use
> MS Internet Explorer to be sure DAP would work... right?
>
> 6 - What issues may we run into using DAP to make our data base
> accessable to a field sales force on the net?
>
> 7 - Is it a major project to take an existing dB and put it on the net
> using DAP?
>
> Thanks for any help in jump starting me on this.
>
> Mel

DAPs are strictly for intranet not internet. Anyone use uses the web page has
to have certain Office components installed. They are very basic in terms of
functionality compared to a real Access form.

My advice is don't bother. Proper web applications need to be written using web
application technologies. Access is not one of them.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Thanks Rick... Groan!

I guess that means we must use some program to remotely run the
database... like Citrix Terminal Server... right?

Or else we have to rebuild all our stuff in ASP... then maintain both
the internal 'Front End' and the Internet ASP pages... Big Groan!

Suggestions? (Please!)

thanks,

Mel

Mel <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> I guess that means we must use some program to remotely run the
> database... like Citrix Terminal Server... right?
>
> Or else we have to rebuild all our stuff in ASP... then maintain
> both the internal 'Front End' and the Internet ASP pages... Big
> Groan!
>
> Suggestions? (Please!)

Windows Terminal Server is the easiest and it will be the cheapest,
too. And you sacrifice no ease of use.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/