We have set up DAPs for Internet use. All configuration for internet use
instructions were followed. The DAPs were tested both inside our network and
outside over the internet.
DAPs were created in Access 2000. Testing showed that they worked over the
internet, connecting to our SQL server 7.0 database, and functioning in an
Office XP professional client machine running Windows XP professional,
outside of our network. Fine.
Further testing with other machines running Office XP standard on Windows XP
professional machines, however, resulted in the error message which states
that "This page has been saved on a web server that is not configured to
allow connections to data source."
Why would this occur on some machines and not others? If it works ok on
some machines, how could the error message be correct?
The MS documentation on deploying DAPs is a bit vague on whether or not
users and developers must be using the same Office version, 2000 or XP.
Could cross-Office use simply mean less reliability, rather than
non-usability?
Also, the MS documentation is vague on whether or not the database server
must be running IIS, as well as the web server. Our DAPs are on a web server
running Windows 2000 (with IIS 5.0), but our SQL server 7.0 database is
running on an NT 4.0 machine. Would running IIS on both machines make the
DAPs more reliable in cross-Office situations (2000 and XP, at least)? Are
cross-Office situations to be necessarily avoided? Would that help? Would
converting the Office 2000 DAPs by opening for edit and saving them in an
Office XP database help them to be more reliable in Office XP?
I see a lot of talk about deploying DAPs over the internet on a Google
search, but few get very much further than describing "how to". No real
troubleshooting.
DAPs over the internet could be much more prevalent and extremely useful for
special situations. If only they were not so troublesome! Does anyone have
any greater experience with DAPs over the internet than we do?
