Access db search result behaviour

Hi all.

The following search was built with frontpage 2002 to query an
Access table. At the moment it insists on a value in both
fields or returns an error. How do I write this so an answer
in either one or none or all fields produces an answer.
i.e. if no fields of the search form are completed the entire
table is the result, and if one or more fields are completed
it simply 'narrows' the search?

<td><b>AGE</b></td>
<td><input TYPE="TEXT" NAME="AGE" VALUE="<%=Request("AGE")%>"
size="20"></td>
</tr>
<td><b>CITY</b></td>
<td><input TYPE="TEXT" NAME="CITY" VALUE="<%=Request("CITY")%>"
size="20"></td>

These are only two of the fields here for illustration but there
are more in the search

Many thanks for any pointers
Richard Rosser [ Fr, 25 August 2006 13:31 ] [ ID #1444406 ]

Re: Access db search result behaviour

"Richard Rosser" <setonendell [at] ntlworld.com> wrote in message
news:5cBHg.13390$_06.2806 [at] newsfe4-gui.ntli.net...
> Hi all.
>
> The following search was built with frontpage 2002 to query an
> Access table. At the moment it insists on a value in both
> fields or returns an error. How do I write this so an answer
> in either one or none or all fields produces an answer.
> i.e. if no fields of the search form are completed the entire
> table is the result, and if one or more fields are completed
> it simply 'narrows' the search?
>
> <td><b>AGE</b></td>
> <td><input TYPE="TEXT" NAME="AGE" VALUE="<%=Request("AGE")%>"
> size="20"></td>
> </tr>
> <td><b>CITY</b></td>
> <td><input TYPE="TEXT" NAME="CITY" VALUE="<%=Request("CITY")%>"
> size="20"></td>
>
> These are only two of the fields here for illustration but there
> are more in the search

How does "it insist"? Show us that code.

I'm not familiar with "Request()"; I have heard of "Request.Cookies()"
"Request.Form()", "Request.QueryString()", Request.ServerVariables()".

URL:http://www.w3schools.com/asp/asp_ref_request.asp

URL:http://www.netzone.ch/caspdoc/Ch9_ASPBuiltIn30.html
McKirahan [ Fr, 25 August 2006 14:04 ] [ ID #1444407 ]

Re: Access db search result behaviour

"McKirahan" <News [at] McKirahan.com> wrote in message
news:vcmdnd5Wyft-e3PZnZ2dnUVZ_oqdnZ2d [at] comcast.com...
> "Richard Rosser" <setonendell [at] ntlworld.com> wrote in message
> news:5cBHg.13390$_06.2806 [at] newsfe4-gui.ntli.net...
> > Hi all.
> >
> > The following search was built with frontpage 2002 to query an
> > Access table. At the moment it insists on a value in both
> > fields or returns an error. How do I write this so an answer
> > in either one or none or all fields produces an answer.
> > i.e. if no fields of the search form are completed the entire
> > table is the result, and if one or more fields are completed
> > it simply 'narrows' the search?
> >
> > <td><b>AGE</b></td>
> > <td><input TYPE="TEXT" NAME="AGE" VALUE="<%=Request("AGE")%>"
> > size="20"></td>
> > </tr>
> > <td><b>CITY</b></td>
> > <td><input TYPE="TEXT" NAME="CITY" VALUE="<%=Request("CITY")%>"
> > size="20"></td>
> >
> > These are only two of the fields here for illustration but there
> > are more in the search
>
> How does "it insist"? Show us that code.
>
> I'm not familiar with "Request()"; I have heard of "Request.Cookies()"
> "Request.Form()", "Request.QueryString()", Request.ServerVariables()".

It is the standard search script code written by MS FrontPage when you
generate a page containing DB Table results from an Access Table.
The whole scrit is very long - do you want to see the entire thing?
Richard Rosser [ Fr, 25 August 2006 14:41 ] [ ID #1444408 ]

Here is the entire code

<html>

<head>
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>New Page 1</title>
</head>

<body>

<form BOTID="0" METHOD="POST" ACTION="new_page_1.htm">
<table BORDER="0">
<tr>
<td><b>CITY</b></td>
<td><input TYPE="TEXT" NAME="CITY" VALUE="<%=Request("CITY")%>"
size="20"></td>
</tr>
<tr>
<td><b>AGE</b></td>
<td><input TYPE="TEXT" NAME="AGE" VALUE="<%=Request("AGE")%>"
size="20"></td>
</tr>
</table>
<p><br>
<input TYPE="Submit"><input TYPE="Reset"><!--webbot bot="SaveAsASP"
clientside suggestedext="asp" preview=" " --></p>
<p> </p>
</form>
<table width="100%">
<tbody>
<!--webbot bot="DatabaseRegionStart"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-columntypes="3,202,5,202,202,202,3,3,3,4,5,5,202,202,203"
s-dataconnection="Database1" b-tableformat="TRUE" b-menuformat="FALSE"
s-menuchoice s-menuvalue b-tableborder="FALSE" b-tableexpand="TRUE"
b-tableheader="FALSE" b-listlabels="TRUE" b-listseparator="TRUE"
i-listformat="0" b-makeform="TRUE" s-recordsource="Females"
s-displaycolumns="USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-criteria="[CITY] EQ {CITY} + {AGE} GT {AGE} +" s-order s-sql="SELECT *
FROM Females WHERE (CITY = '::CITY::' AND AGE > ::AGE::)"
b-procedure="FALSE" clientside suggestedext="asp"
s-defaultfields="CITY=&AGE=" s-norecordsfound="No records returned."
i-maxrecords="256" i-groupsize="5" botid="0"
u-dblib="fpweb:///_fpclass/fpdblib.inc"
u-dbrgn1="fpweb:///_fpclass/fpdbrgn1.inc"
u-dbrgn2="fpweb:///_fpclass/fpdbrgn2.inc" tag="TBODY"
preview="<tr><td colspan=64 bgcolor="#FFFF00"
align="left" width="100%"><font
color="#000000">This is the start of a Database Results region.
The region will not work unless the page has a file extension of
".asp".</font></td></tr>"
startspan --><!--#include file="fpweb:///_fpclass/fpdblib.inc"-->
<% if 0 then %>
<SCRIPT Language="JavaScript">
document.write("<div style='background: yellow; color: black;'>The Database
Results component on this page is unable to display database content. The
page must have a filename ending in '.asp', and the web must be hosted on a
server that supports Active Server Pages.</div>");
</SCRIPT>
<% end if %>
<%
fp_sQry="SELECT * FROM Females WHERE (CITY = '::CITY::' AND AGE >
::AGE::)"
fp_sDefault="CITY=&AGE="
fp_sNoRecords="<tr><td colspan=14 align=left width=""100%"">No records
returned.</td></tr>"
fp_sDataConn="Database1"
fp_iMaxRecords=256
fp_iCommandType=1
fp_iPageSize=5
fp_fTableFormat=True
fp_fMenuFormat=False
fp_sMenuChoice=""
fp_sMenuValue=""
fp_iDisplayCols=14
fp_fCustomQuery=False
BOTID=0
fp_iRegion=BOTID
%>
<!--#include file="fpweb:///_fpclass/fpdbrgn1.inc"-->
<!--webbot bot="DatabaseRegionStart" endspan i-checksum="59737" --><tr>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="USER" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>USER<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"USER")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="2478" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="AGE" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>AGE<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"AGE")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="63514" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="CITY" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>CITY<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"CITY")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="75" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="DOMICILE" b-tableformat="TRUE" b-hashtml="FALSE"
b-makelink="FALSE" clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>DOMICILE<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"DOMICILE")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="9689" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="FIRST NAME" b-tableformat="TRUE" b-hashtml="FALSE"
b-makelink="FALSE" clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>FIRST NAME<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"FIRST NAME")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="15653" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="HEIGHT" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>HEIGHT<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"HEIGHT")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="9916" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="WEIGHT" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>WEIGHT<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"WEIGHT")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="10876" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="CHILDREN" b-tableformat="TRUE" b-hashtml="FALSE"
b-makelink="FALSE" clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>CHILDREN<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"CHILDREN")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="8983" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="PREVIOUS M" b-tableformat="TRUE" b-hashtml="FALSE"
b-makelink="FALSE" clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>PREVIOUS M<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"PREVIOUS M")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="16602" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="AGE MIN" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>AGE MIN<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"AGE MIN")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="7172" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="AGE MAX" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>AGE MAX<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"AGE MAX")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="7268" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="SMOKES" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>SMOKES<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"SMOKES")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="11638" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="DRINKS" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>DRINKS<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"DRINKS")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="11342" --></td>
<td>
<!--webbot bot="DatabaseResultColumn"
s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"
s-column="URL" b-tableformat="TRUE" b-hashtml="FALSE" b-makelink="FALSE"
clientside b-MenuFormat preview="<font
size="-1">&lt;&lt;</font>URL<font
size="-1">&gt;&gt;</font>"
startspan --><%=FP_FieldVal(fp_rs,"URL")%><!--webbot
bot="DatabaseResultColumn" endspan i-checksum="673" --></td>
</tr>
<!--webbot bot="DatabaseRegionEnd" b-tableformat="TRUE"
b-menuformat="FALSE" u-dbrgn2="fpweb:///_fpclass/fpdbrgn2.inc"
i-groupsize="5" clientside tag="TBODY" preview="<tr><td colspan=64
bgcolor="#FFFF00" align="left"
width="100%"><font color="#000000">This is the
end of a Database Results
region.</font></td></tr><TR><TD ALIGN=LEFT
VALIGN=MIDDLE COLSPAN=64><NOBR><INPUT TYPE=Button VALUE="
|< "><INPUT TYPE=Button VALUE=" <
"><INPUT TYPE=Button VALUE=" > "><INPUT
TYPE=Button VALUE=" >| ">
[1/5]</NOBR><BR></td></tr>"
startspan --><!--#include file="fpweb:///_fpclass/fpdbrgn2.inc"-->
<!--webbot bot="DatabaseRegionEnd" endspan i-checksum="23298" --></tbody>
</table>

</body>

</html>
Richard Rosser [ Fr, 25 August 2006 14:45 ] [ ID #1444409 ]

Re: Access db search result behaviour

"Richard Rosser" <setonendell [at] ntlworld.com> wrote in message
news:7eCHg.13395$_06.3625 [at] newsfe4-gui.ntli.net...

[snip]

> It is the standard search script code written by MS FrontPage when you
> generate a page containing DB Table results from an Access Table.
> The whole scrit is very long - do you want to see the entire thing?

I'd recommend a Frontpage newsgroup such as microsoft.public.frontpage.
McKirahan [ Fr, 25 August 2006 15:36 ] [ ID #1444410 ]

Re: Here is the entire code

Richard wrote on Fri, 25 Aug 2006 12:45:22 GMT:

> <!--webbot bot="DatabaseRegionStart"
> s-columnnames="ID,USER,AGE,CITY,DOMICILE,FIRST
> NAME,HEIGHT,WEIGHT,CHILDREN,PREVIOUS M,AGE MIN,AGE MAX,SMOKES,DRINKS,URL"

This is bad, FrontPage reveals your table definitions for all the world to
see. While in itself not a security issue, if you had some code that allowed
the SQL to be built on the fly (see further down) then this information can
be used to get more data out of your system without trial and error.

> s-recordsource="Females"

and here's the table name visible to the public.


> fp_sQry="SELECT * FROM Females WHERE (CITY = '::CITY::' AND AGE >
> ::AGE::)"

Well here's your problem - FP is forcing both the CITY and AGE values to be
required.


Hopefully the FP database bot has some kind of data validation, if it just
passes values straight in then this sort of thing would be bad:

CITY=anywhere&AGE=10%29;DELETE+FROM+Females+WHERE+%281%3D1

which could result in the following query running:


SELECT * FROM Females WHERE (CITY = 'anywhere' AND AGE > 10);DELETE FROM
Females WHERE 1=1)


As you can see, that's potentially devastating.


This entire thing should be written from scratch using a stored procedure
and passing values in by parameter. FrontPage does not create easily
maintainable code, and reveals way too much information to the public.


Dan
Daniel Crichton [ Mo, 04 September 2006 18:04 ] [ ID #1454732 ]

Re: Access db search result behaviour

"McKirahan" <News [at] McKirahan.com> wrote in message
news:vcmdnd5Wyft-e3PZnZ2dnUVZ_oqdnZ2d [at] comcast.com...
> "Richard Rosser" <setonendell [at] ntlworld.com> wrote in message
> news:5cBHg.13390$_06.2806 [at] newsfe4-gui.ntli.net...
>> Hi all.
>>
>> The following search was built with frontpage 2002 to query an
>> Access table. At the moment it insists on a value in both
>> fields or returns an error. How do I write this so an answer
>> in either one or none or all fields produces an answer.
>> i.e. if no fields of the search form are completed the entire
>> table is the result, and if one or more fields are completed
>> it simply 'narrows' the search?
>>
>> <td><b>AGE</b></td>
>> <td><input TYPE="TEXT" NAME="AGE" VALUE="<%=Request("AGE")%>"
>> size="20"></td>
>> </tr>
>> <td><b>CITY</b></td>
>> <td><input TYPE="TEXT" NAME="CITY" VALUE="<%=Request("CITY")%>"
>> size="20"></td>
>>
>> These are only two of the fields here for illustration but there
>> are more in the search
>
> How does "it insist"? Show us that code.
>
> I'm not familiar with "Request()"; I have heard of "Request.Cookies()"
> "Request.Form()", "Request.QueryString()", Request.ServerVariables()".
>
> URL:http://www.w3schools.com/asp/asp_ref_request.asp
>
> URL:http://www.netzone.ch/caspdoc/Ch9_ASPBuiltIn30.html
>
>

Request.Form is the default. so Request() does the same thing
Jimmy [ Di, 12 September 2006 18:12 ] [ ID #1463677 ]

Re: Access db search result behaviour

"Jimmy" <j [at] j.j> wrote in message
news:eKuMOZo1GHA.4388 [at] TK2MSFTNGP03.phx.gbl...
>

[snip]

> > I'm not familiar with "Request()"
>
> Request.Form is the default. so Request() does the same thing

That may be but it's bad practice -- IMO.

Also:

"If a variable with the same name exists in more than one collection,
the Request object returns the first instance that the object encounters."
McKirahan [ Di, 12 September 2006 18:37 ] [ ID #1463678 ]

Re: Access db search result behaviour

Jimmy wrote:
> "McKirahan" <News [at] McKirahan.com> wrote in message
> news:vcmdnd5Wyft-e3PZnZ2dnUVZ_oqdnZ2d [at] comcast.com...
> > "Richard Rosser" <setonendell [at] ntlworld.com> wrote in message
> > news:5cBHg.13390$_06.2806 [at] newsfe4-gui.ntli.net...
> >> Hi all.
> >>
> >> The following search was built with frontpage 2002 to query an
> >> Access table. At the moment it insists on a value in both
> >> fields or returns an error. How do I write this so an answer
> >> in either one or none or all fields produces an answer.
> >> i.e. if no fields of the search form are completed the entire
> >> table is the result, and if one or more fields are completed
> >> it simply 'narrows' the search?
> >>
> >> <td><b>AGE</b></td>
> >> <td><input TYPE="TEXT" NAME="AGE" VALUE="<%=Request("AGE")%>"
> >> size="20"></td>
> >> </tr>
> >> <td><b>CITY</b></td>
> >> <td><input TYPE="TEXT" NAME="CITY" VALUE="<%=Request("CITY")%>"
> >> size="20"></td>
> >>
> >> These are only two of the fields here for illustration but there
> >> are more in the search
> >
> > How does "it insist"? Show us that code.
> >
> > I'm not familiar with "Request()"; I have heard of "Request.Cookies()"
> > "Request.Form()", "Request.QueryString()", Request.ServerVariables()".
> >
> > URL:http://www.w3schools.com/asp/asp_ref_request.asp
> >
> > URL:http://www.netzone.ch/caspdoc/Ch9_ASPBuiltIn30.html
> >
> >
>
> Request.Form is the default. so Request() does the same thing

You miss the point. You shouldn't use Request() without qualifying the
collection you are referring to. It's sloppy, and potentially very
inefficient.

--
Mike Brind
Mike Brind [ Di, 12 September 2006 18:42 ] [ ID #1463679 ]
Webserver » microsoft.public.inetserver.asp.db » Access db search result behaviour

Vorheriges Thema: access stored query problem
Nächstes Thema: Select query