published database

[Anonyma]

I have a frontpage development directory containing:-
1. An Access 2000 database (in the fpdb subdirectory).
2. A number of hand coded javascript .asp files to read from and write to this database.

I have published the development directory to a published directory (c:\inetpub\wwwroot).

When a web user uses the .asp files to update the database, then (quite naturally) it is the published copy of the database that gets updated, not the development copy.

This seems to imply that, once published, future updates to the database should be made to the published copy and not the local development copy.
Q1). Have I understood this right?

Q2). Is there anything to be gained in splitting the database into a front-end (containing queries) and a back-end (containing the tables) so that both development copy and published copy see the same dataset?
When I tried to do this, it didn't work as the front-end tables were still linked to the
development directory database, using the development directory pathname. The error message was:
Error Type:
Microsoft JET Database Engine (0x80004005)
'D:\developmentdirectory\fpdb\backend.mdb' is not a valid path.

 

[Stefan B Rusynko]

In order to run a DB (and ASP) you need to be using a server based web
- you do not publish to a disc based web at c:\inetpub\wwwroot
- you publish to and open the local server based web for that location
http://localhost/ or http://yourmachinename/

You can not, and should not, be using frontend/backend DBs in the web server
- use a complete DB w/ you date and queries in it in your fpdb folder in the localhost fpdb folder
(or use a DSN pointing to a DB on your PC at another location)
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


|I have a frontpage development directory containing:-
| 1. An Access 2000 database (in the fpdb subdirectory).
| 2. A number of hand coded javascript .asp files to read from and write to this database.
|
| I have published the development directory to a published directory (c:\inetpub\wwwroot).
|
| When a web user uses the .asp files to update the database, then (quite naturally) it is the published copy of the database that
gets updated, not the development copy.
|
| This seems to imply that, once published, future updates to the database should be made to the published copy and not the local
development copy.
| Q1). Have I understood this right?
|
| Q2). Is there anything to be gained in splitting the database into a front-end (containing queries) and a back-end (containing the
tables) so that both development copy and published copy see the same dataset?
| When I tried to do this, it didn't work as the front-end tables were still linked to the
| development directory database, using the development directory pathname. The error message was:
| Error Type:
| Microsoft JET Database Engine (0x80004005)
| 'D:\developmentdirectory\fpdb\backend.mdb' is not a valid path.
|

 

[uzroks]

Agreed - let me explain my setup in more detail:-
1. I am developing the web interface and database on my own PC, and it
has IIS installed.
2. The web interface and database will eventually be hosted on a
company web server.
3. The default website on my PC lives at http://mypcname from the
intranet perspective, and c:\inetpub/wwwroot from my local PC's
perspective.
4. When I access the .asp pages I do so through http://mypcname (so
that server side javascript to access the database gets executed).
5. I am using ODBC Data Source Administrator to reference my database
as a System DSN.

I can read from the database ok. It is updating the database (from the
web) that I'm curious about. It seems quite logical that only the
published copy of the database gets updated. Its just that once the
database is published and updated from the web, it seems to me that the
published database becomes the 'latest' version - and the development
version becomes out of date. Any further updates (from the development
PC) need to be done to the published version only, and the development
version ceases to be of any use.
Am I right in my understanding of this?

 

[Thomas A. Rowe]

The published/live database is the one that is updated, you will need to work on the live site and
disable any write access to the database while working on it.

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

Agreed - let me explain my setup in more detail:-
1. I am developing the web interface and database on my own PC, and it
has IIS installed.
2. The web interface and database will eventually be hosted on a
company web server.
3. The default website on my PC lives at http://mypcname from the
intranet perspective, and c:\inetpub/wwwroot from my local PC's
perspective.
4. When I access the .asp pages I do so through http://mypcname (so
that server side javascript to access the database gets executed).
5. I am using ODBC Data Source Administrator to reference my database
as a System DSN.

I can read from the database ok. It is updating the database (from the
web) that I'm curious about. It seems quite logical that only the
published copy of the database gets updated. Its just that once the
database is published and updated from the web, it seems to me that the
published database becomes the 'latest' version - and the development
version becomes out of date. Any further updates (from the development
PC) need to be done to the published version only, and the development
version ceases to be of any use.
Am I right in my understanding of this?

In order to run a DB (and ASP) you need to be using a server based web
- you do not publish to a disc based web at c:\inetpub\wwwroot
- you publish to and open the local server based web for that location
http://localhost/ or http://yourmachinename/

You can not, and should not, be using frontend/backend DBs in the web server
- use a complete DB w/ you date and queries in it in your fpdb folder in the localhost fpdb
folder
(or use a DSN pointing to a DB on your PC at another location)
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

 

[David Berry]

Or publish it back down, make updates to the database and publish it back
up. You'd have to make sire that people on the live site aren't also making
changes once you've published down so that it doesn't get out of sync. You
could do this by having a page that says something like "Site Temporarily
Down for Database Maintenance" and make this the default page until you've
published the database back up.

The published/live database is the one that is updated, you will need to
work on the live site and disable any write access to the database while
working on it.

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

Agreed - let me explain my setup in more detail:-
1. I am developing the web interface and database on my own PC, and it
has IIS installed.
2. The web interface and database will eventually be hosted on a
company web server.
3. The default website on my PC lives at http://mypcname from the
intranet perspective, and c:\inetpub/wwwroot from my local PC's
perspective.
4. When I access the .asp pages I do so through http://mypcname (so
that server side javascript to access the database gets executed).
5. I am using ODBC Data Source Administrator to reference my database
as a System DSN.

I can read from the database ok. It is updating the database (from the
web) that I'm curious about. It seems quite logical that only the
published copy of the database gets updated. Its just that once the
database is published and updated from the web, it seems to me that the
published database becomes the 'latest' version - and the development
version becomes out of date. Any further updates (from the development
PC) need to be done to the published version only, and the development
version ceases to be of any use.
Am I right in my understanding of this?

In order to run a DB (and ASP) you need to be using a server based web
- you do not publish to a disc based web at c:\inetpub\wwwroot
- you publish to and open the local server based web for that location
http://localhost/ or http://yourmachinename/

You can not, and should not, be using frontend/backend DBs in the web
server
- use a complete DB w/ you date and queries in it in your fpdb folder in
the localhost fpdb folder
(or use a DSN pointing to a DB on your PC at another location)
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________

 

[uzroks]

Ok, that has clarified it for me. Thanks to all responders.