N
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.
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.