Opening an Access database in FP

[Nicholas Savalas - http://savalas.tv]

I'm so glad I held onto my copy of FP 2000. In that older version, one
could double click on the Access (.mdb) file, and it would open in
Access for you to edit. FP2003 does not allow you to do that in very
secure Windows 2003 servers. I know all about the security flaws, all
about the more efficient and more advanced methods of editing your
database using ASP/ASP.net/VB/etc code, but jeez, I miss the days where
I was three clicks away from adding or renaming a column on a web based
database. Of course, the database interface wizard included is not
worth diddly unless you set ALL the variables correctly upfront first.
I mean, anticipating every possible query, defining and properly naming
every possible quantity and value, and being practically precient in
predicting every possible report that a client might want. Yes, I have
built hundreds of web sites that include secure administration areas
with online database editors, but I would like to know what software
engineer decided that I should have to publish my database locally,
edit it, and then put it back on the site. This is not to mention the
hassle that is involved if that database is in use constantly, because
the .ldb file that locks the database while it is in use (for example,
one that is collecting stats or rotating banners) in the fpdb folder
and use proprietary connections provided by FP (which we all love to
hate) make re-importing the database impossible. Often, you have to
delete the original connection and create an entirely new connection
with an entirely different name.

Another beef that I have is their proprietary code inserts involving
borders :

<meta name="Microsoft Border" content="tlb, default">
<meta name="Microsoft Theme" content="blablabla 1011">

These attributes can not take a space-separated list of words as a
value, but only one word ("token"). This may also be caused by the use
of a space for the value of an attribute which does not permit it.
These tags are not valid HTML 4+/XHTML. We all know how to get rid of
them, but don't you think Microsoft would have visited
http://validator.w3.org/ by now?

Actually, I should be thanking Microsoft. It was these flaws that
forced me to learn ASP/ASP.net/VB/etc code in the first place to
resolve these built in issues. There's no question that FP is the most
powerful HTML editor in use today, but it is too bad that is useless
without notepad. Users, keep that copy of FP2000, just in case. And
put notepad in your quick lauch toolbar.

 

[Andrew Murray]

That's what the Database Interface Wizard is for; to edit the DB online
through a web page interface.

 

[Nicholas Savalas - http://savalas.tv]

Dear Andrew,
Thank you for your reply, you are most kind - but you must be crazy.
No self respecting site/app developer would be caught dead using that
thing. I know of about twenty jokes where the punch line is 'database
interface wizard'. Entire web sites are devoted to work arounds to it -
including some very talented coders (see
http://www.spiderwebwoman.com/resources/dbrwtipsandtricks.asp - for
example). My original post was written hoping to catch the attention of
someone who has some influence in software design at Microsoft. Maybe
start a fist fight over there. Because everybody knows that Microsoft
FP doesn't like to play nice with the other children. Admit it, daddy
has two left feet.

 

[Stefan B Rusynko]

Your past practice of opening an access DB directly in a server based web (local or remote) is dangerous and can often lock up or
crash the server (or corrupt the DB)
- especially if the DB is in use by anyone on your site when you do it
Just right click it, export it to your desktop or some other folder, edit it, and then File import it again
- like it or not, that is the correct way to do it

As for the FP 2 design time tags
<meta name="Microsoft Border" content="tlb, default">
<meta name="Microsoft Theme" content="blablabla 1011">
They are webbot that generate lots of other code that will never validate
- don't use them if you want validatable code
Most of the webbot code will never validate as they are not intended for the serious developers
(especially themes and shared borders)
- they are shortcuts for average users that don't know how, or don't want to learn how to hand code

--

_____________________________________________
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'm so glad I held onto my copy of FP 2000. In that older version, one
| could double click on the Access (.mdb) file, and it would open in
| Access for you to edit. FP2003 does not allow you to do that in very
| secure Windows 2003 servers. I know all about the security flaws, all
| about the more efficient and more advanced methods of editing your
| database using ASP/ASP.net/VB/etc code, but jeez, I miss the days where
| I was three clicks away from adding or renaming a column on a web based
| database. Of course, the database interface wizard included is not
| worth diddly unless you set ALL the variables correctly upfront first.
| I mean, anticipating every possible query, defining and properly naming
| every possible quantity and value, and being practically precient in
| predicting every possible report that a client might want. Yes, I have
| built hundreds of web sites that include secure administration areas
| with online database editors, but I would like to know what software
| engineer decided that I should have to publish my database locally,
| edit it, and then put it back on the site. This is not to mention the
| hassle that is involved if that database is in use constantly, because
| the .ldb file that locks the database while it is in use (for example,
| one that is collecting stats or rotating banners) in the fpdb folder
| and use proprietary connections provided by FP (which we all love to
| hate) make re-importing the database impossible. Often, you have to
| delete the original connection and create an entirely new connection
| with an entirely different name.
|
| Another beef that I have is their proprietary code inserts involving
| borders :
|
| <meta name="Microsoft Border" content="tlb, default">
| <meta name="Microsoft Theme" content="blablabla 1011">
|
| These attributes can not take a space-separated list of words as a
| value, but only one word ("token"). This may also be caused by the use
| of a space for the value of an attribute which does not permit it.
| These tags are not valid HTML 4+/XHTML. We all know how to get rid of
| them, but don't you think Microsoft would have visited
| http://validator.w3.org/ by now?
|
| Actually, I should be thanking Microsoft. It was these flaws that
| forced me to learn ASP/ASP.net/VB/etc code in the first place to
| resolve these built in issues. There's no question that FP is the most
| powerful HTML editor in use today, but it is too bad that is useless
| without notepad. Users, keep that copy of FP2000, just in case. And
| put notepad in your quick lauch toolbar.
|