Can frontpage update the live mdb when publishing, so records don't get wiped out?

[z3ph3r]

I'm new to Frontpage databases, and my main goal is simple. I want to
be able to update my ASP pages and the live fpdb\mdb (located on the
web hosting server) without losing customer records. Right now, when I
make updates to the database and publish them, it overwrites the mdb
file on the live site, wiping out customer records.

I tried marking the local mdb file as "don't publish", but then my ASP
pages are feeding data to a live mdb that hasn't been updated, and I
then run into lots of problems.

Not knowing what to do next, I created an Access db via my web hosting
control panel, and I had my web hosting service setup a DSN on their
server to point to this mdb file. They told me I could access it via
ftp, but I'm not sure where to go from here so that FP will work with
this live mdb file instead of the local fpdb\mdb file on my
workstation. How do my ASP pages know to post content to the live mdb,
rather than the local mdb? Do I edit the global.asa file so that it
somehow uses the DSN created by my web hosting service? Or is there a
better way to let FP create its own db and somehow make FP work with
the live mdb rather than a local copy?

Hope that makes sense. Obviously, I'm new to dealing with FP and
database integration / publishing. I've thought about trying to open
the entire live website in FP, if that's possible, so that I'm working
with the same mdb that is live, but I've heard there are drawbacks to
doing this, such as a customer posting data while I'm updating the mdb,
etc.

Any help would be appreciated. Thanks!

 

[Thomas A. Rowe]

If you have user update the database on live/remote server, then you can not upload your local copy
without overwriting those changes. You would need to edit the database via ASP pages on the
live/remote server

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
==============================================
Agents Real Estate Listing Network
http://www.NReal.com
==============================================

 

[z3ph3r]

Thanks Thomas. I appreciate the feedback.

Z

If you have user update the database on live/remote server, then you can not upload your local copy
without overwriting those changes. You would need to edit the database via ASP pages on the
live/remote server

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
==============================================
Agents Real Estate Listing Network
http://www.NReal.com
==============================================

 

[et]

The challenge though is this:
Everytime you use FP to update new wab pages to the server, the current
content of the Access DB will be updated to the server, overweiting any new
data customers added to the online DB since the previous update.

So the question is really how to update the server version without pushing
local DB.

ed

 

[David Berry]

Mark the local database as Do Not Publish. Right-click on the mdb file,
choose properties, Workgroup tab and then check the box to exclude the file
from publishing.

 

[et]

Thanks David... however, only two tabs available: General & Summary. Neither
provide the do not publish capability.

Ed

 

[Trevor L.]

Thanks David... however, only two tabs available: General & Summary.
Neither provide the do not publish capability.

Ed

I am not quite sure of the context, but to mark a file as Do Not Publish,
right click on the file name in the Folders View and select "Don't Publish"

On my (local) website, clicking Properties on an .mdb file shows 3 tabs, so
maybe something else is wrong.

--
Cheers,
Trevor L.
[ Microsoft MVP - FrontPage ]
MVPS Website: http://trevorl.mvps.org/
----------------------------------------

 

[David Berry]

What version of FrontPage are you using? Are you in Folder View?

 

[David Berry]

I just noticed that you posted this question in another thread and it looks
like you were able to mark it Do not Publish. In the future please don't
ask the same questions in multiple threads since it makes it harder for
people to follow the replies and see if you have been helped.