Publishing databases

[Randy Morgan]

Databases are cool. I'm starting to use them on my site, but am unsure
of the best protocol for managing them from within FP.

So far, these are all MS Access databases, if that matters.

I'm doing this design iteratively, by which I mean that once I get one
part of a form working and writing properly to the database I want to
move on to the next thing. Here's the process I've been using:

1. Create a database outside FP using MS Access.
2. Import the database from within FP in to the fpdb directory.
3. Publish the site.
4. See if I can post my form data to do it from the site.

Assuming I get through this OK, I'm not sure of the best procedure for
the next iteration of the design. I think I will be adding things over
time, so there will be data in the database that I don't want to lose.

To get the database back for editing, I assume I just publish from
remote to local, correct? To edit the database (by, for example, adding
a new table for new form data), should I open the database using Access
from within FP, or should I open the database from outside of FP, or do
I first need to move or copy the database outside of my disk's website
before doing anything and then re-import when I'm done editing? And,
how does FP know when to publish/overwrite the database to the remote
web? Do I need to mark it as Do Not Publish after the first publish so
it doesn't overwrite the remote file?

Thanks,

 

[Stefan B Rusynko]

No need to publish the site & DB if it is in the default FP folder (fpdb) in your site (local or remote)
- but that will update a DB (provided your DB is not too large)

Select the DB and use File Export (say to your desktop)
Open it in Access and add your tables / fields
Then back in FP File Import it (back into the correct folder to overwrite the original)

And yes you can mark the DB in your local as do not publish (if you are working say remotely),
and then periodically update it too (by same steps as above or publishing)

Just be aware if you are working in a live site and other users have access to pages that open the DB, you could crash the site if
you update your DB while it is opened by them (especially for writes)
- that's why it is best to test offline and stop the site to update the DB online once in production

--




| Databases are cool. I'm starting to use them on my site, but am unsure
| of the best protocol for managing them from within FP.
|
| So far, these are all MS Access databases, if that matters.
|
| I'm doing this design iteratively, by which I mean that once I get one
| part of a form working and writing properly to the database I want to
| move on to the next thing. Here's the process I've been using:
|
| 1. Create a database outside FP using MS Access.
| 2. Import the database from within FP in to the fpdb directory.
| 3. Publish the site.
| 4. See if I can post my form data to do it from the site.
|
| Assuming I get through this OK, I'm not sure of the best procedure for
| the next iteration of the design. I think I will be adding things over
| time, so there will be data in the database that I don't want to lose.
|
| To get the database back for editing, I assume I just publish from
| remote to local, correct? To edit the database (by, for example, adding
| a new table for new form data), should I open the database using Access
| from within FP, or should I open the database from outside of FP, or do
| I first need to move or copy the database outside of my disk's website
| before doing anything and then re-import when I'm done editing? And,
| how does FP know when to publish/overwrite the database to the remote
| web? Do I need to mark it as Do Not Publish after the first publish so
| it doesn't overwrite the remote file?
|
| Thanks,
| --
| Randy Morgan