📄 readme.htm
字号:
similar. For DATAADMI.MDB it is "admin". If
the database neither has a user ID nor a password,
leave this field blank.</font></p>
<p align="left"><font size="2"><strong>Database
Password.</strong><br>
Input the database password here if there exists one.
For DATAADMI.MDB it is "dataadmin". If the
database neither has a user ID nor a password leave
this field blank.</font></p>
<p align="left"><font size="2"><strong>Table Name.</strong><br>
Input a valid table name for the database here. The
table for DATAADMI.MDB is "dataadmin".</font></p>
<p align="left"><font size="2"><strong>Ascending
Order by Field.</strong><br>
Optional input. If you are looking for a particular
record listing the table entries in ascending order
by a particular field may help. Of course, this value
must be a valid field name for the table.</font></p>
<p align="left"><font size="2"><strong>Descending
Order by Field.</strong><br>
Optional input. If you are looking for a particular
record listing the table entries in descending order
by a particular field may help. Of course, this value
must be a valid field name for the table.</font></p>
<p align="left"><font size="2">DataAdmin will return
an ERROR if any of the above information is invalid.
A user must input the correct information in order to
use DataAdmin. See Use_Cook variable in GLOBVARS.ASP
to help.</font></p>
</blockquote>
<p align="left"><a name="Additional Setup Options"><font
color="#FF0000" size="3"><strong>Additional Setup Options</strong></font></a></p>
<blockquote>
<p align="left"><font size="2"><strong>1. </strong>Edit
GLOBVARS.ASP for other options to change names,
passwords, redirection page url, home page url,
etc...See below</font></p>
</blockquote>
<p align="left"><a name="Global variable definitions"><font
color="#FF0000" size="3"><strong>Global variable
definitions</strong></font></a></p>
<blockquote>
<p align="left"><font size="2"><strong>LogiName</strong><br>
"Login Name" is the name users must use to
log in succesfully to Data Admin.</font></p>
<p align="left"><font size="2"><strong>LogiPass</strong><br>
"Login Password" is the password users must
useto log in successfully to Data Admin.</font></p>
<p align="left"><font size="2"><strong>RediPage</strong><br>
"Redirection Page" is the URL that pages
will use when a user tries call on of the Data Admin
pages without the proper authority. This typically
will be your home page URL.</font></p>
<p align="left"><font size="2"><strong>HomePage</strong><br>
"Home Page" is the URL that
"Home" will link to thoughout the Data
Admin pages.</font></p>
<p align="left"><font size="2"><strong>Use_Cook</strong><br>
"Use Cookies" denotes whether Data Admin
should or should not use cookies to save information
from the login page. Passwords are not save in
cookies.</font></p>
<p align="left"><font size="2"><strong>CookFile</strong><br>
"Cookie file name" is the name, along with
the website URL, all cookies are saved for the
discussion group. ASP-DataAdmin uses cookies to save
login information for users' convenience.</font></p>
<p align="left"><font size="2"><strong>NumbRecoPage</strong><br>
"Number Records Page" is the number of
records to display on the data listing page. Must be
greater than 1.</font></p>
</blockquote>
<p align="left"><a name="History - Enhancements/Bugs"><font
color="#FF0000" size="3"><strong>History -
Enhancements/Bugs</strong></font></a></p>
<blockquote>
<p align="left"><font size="2"><strong>Version 1.1<br>
a.</strong> Bug. Fixed the handling of Null values
for fields in editing records.<br>
<strong>b.</strong> Bug. Previous version assumed the
auto increment field was always the first field when
updating records. Very bad assumption!<br>
<strong>c.</strong> Enhancement. Included the global
variable NumbRecoPage.</font></p>
</blockquote>
<p align="left"><a name="Naming Conventions"><font
color="#FF0000" size="3"><strong>Naming Conventions</strong></font></a></p>
<blockquote>
<p align="left"><font size="2"><strong>1.</strong>
General. I believe the first four characters of most
words are usually descriptive enough to remind the
reader what a word is when used in variable names.
Therefore, I use this "four-character" rule
for file, function, and variable names for three
reasons. One, it creates a consistent naming
convention. Two, it usually gives enough information
to suggest to the reader what the name means. Three,
it helps reduce the size of .ASP files.</font></p>
<p align="left"><font size="2"><strong>2.</strong>
File Names. ASP files are named using four-character
rule of the most two descriptive words I can come up
with for that file. i.e.<br>
insemess.asp is "Insert Message"<br>
dispthre.asp is "Display Thread"<br>
commfunc.asp is "Common Functions.</font></p>
<p align="left"><font size="2"><strong>3.</strong>
Function Names. Again I use the four-character rule
of the 2-3 most descriptive words for the function
with a '_' between each word. i.e.<br>
open_data() is "Open Database"<br>
upda_info() is "Update Info Table"<br>
save_emai_addr() is "Save Email Address".</font></p>
<p align="left"><font size="2"><strong>4.</strong>
Global or Public Variable Names. Global variables use
the four-character rule with the first character of
each four letters in upper case. i.e.<br>
SearStri is "Search string"<br>
PageNumb is "Page Number"<br>
AutoNumb is "Auto Number"<br>
Conn is "Connection"</font></p>
<p align="left"><font size="2"><strong>5.</strong>
Local or Function Variable Names. Local variables can
and should be treated differently because they are
used in a relatively small section of code.
Therefore, if they are appropriately defined (or the
definition is obvious), then it is not important to
have a long descriptive name. As such, all local and
function variables are restricted to one or two
characters and are always lower case. The letter may
signify the beginning of a descriptive word but do
not always. Another benefit of this approach is that
there should never be a conflict with global and
local variables..</font></p>
</blockquote>
<p align="left"><a name="Create a child web"><font
color="#FF0000" size="3"><strong>Create a child web</strong></font></a></p>
<blockquote>
<p align="left"><font size="2"><strong>1.</strong>
Open your root web in FrontPage Explorer.<br>
<strong>2.</strong> Create a new folder using the
name you want for you child web.<br>
<strong>3.</strong> Click on "File, New
FrontPage Web".<br>
<strong>4.</strong> Select from Wizard or Template:
"Empty Web." <br>
<strong>5.</strong> Give it a title with the same
name and case of the sub folder you created from 2
above. i.e. "disc", "images"...<br>
<strong>6.</strong> Make sure server path is correct.
i.e. "www.domain.com." This does not
include the folder name.<br>
<strong>7.</strong> Make sure "Add to Existing
Web" is unchecked. <br>
<strong>8.</strong> Click OK. </font></p>
</blockquote>
</td>
</tr>
</table>
</center></div>
</body>
</html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -