Opening a Database in FP 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In FP 2002 I was able to open an Access db directly through the UI. After upgrading to FP 2003, I receive an error message when ever I try to open the same DB file. "This file is located outside your intranet or on an untrusted site. Microsoft Access will not open the file due to potential security problems.

I could FTP the file, view/changed/etc... then upload but the previous functionality would be better

Any suggestions

Ian Anderson
 
Under IE make the site a trusted site.

MS is tightening security on all products.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================


Ian Anderson said:
In FP 2002 I was able to open an Access db directly through the UI. After
upgrading to FP 2003, I receive an error message when ever I try to open the
same DB file. "This file is located outside your intranet or on an
untrusted site. Microsoft Access will not open the file due to potential
security problems."
 
If you are using the database to handle your shopping cart, etc. then you
should either create a set of Admin pages to allow you to manage the
database directly online., as once the site is live. If you open the
database directly in Access on live site, most likely site users will be
lock out of the database.

If you need to do major updating, then it is best to temporarily disable any
functions using the database, then download the database via FP's Export
command or via a FTP application.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================


Ian Anderson said:
The site is http://www.advantagemedicalpro.com. I have entered it in as a
trusted site under IE. I entered it ass HTTP:// as well as HTTPS://. Still
getting the same error message.
 
Back
Top