Sending ASP variable to Database Results Wizard query

[Michael Rothstein]

Is it possible to create a variable in ASP and then pass it into a Database
Results Wizard query?

I've got a variable "myquery" that I've assembled in ASP. I thought I could
do this:

SELECT * FROM mytable WHERE ::myquery::

Is the problem that I can only use variables that come from submitted forms
or am I missing something?

Thanks.

 

[TB]

Since WHERE is used for narrowing a recordset, I suggest you only use your
variable as the limiting argument, not the entire WHERE statement.
Furthermore, I suggest you to specify the columns to be used, and not
everything. So perhaps you could do something like this:

(DB Connection DBConn already established)
<%
dim strSQL, wherelimit
wherelimit = "whatever"
StrSQL = "SELECT column1, column2 FROM mytable WHERE column1 ='" &
wherelimit & "'
Set RS = Server.CreateObject("ADODB.Recordset")
RS.Open StrSQL, DBConn, 1,3
Response.write "Here''s the result of your query: " & "<br>"
Do while not RS.EOF
response.write RS("column1") & "<br>"
response.write RS("column2") & "<br>"
RS.MoveNext
Loop
RS.Close
Set RS = Nothing
DBConn.close
Set DBConn = nothing
%>

Cheers,

TB

 

[Michael Rothstein]

Thanks for your reply.

I was hoping to build my query using ASP and then dropping it into the DRW
to narrow my recordset as shown in the query of my first message. It looks
like your code is used independently of DRW and is used to establish my DB
connection, however I was trying to see if I could use DRW and then pass my
ASP variable (which I'd build up in a script) to it.

Is that possible (regardless of whether it's better or worse) or do I need
to do the entire thing in ASP and forget about using DRW?

MR

 

[TB]

As much as I like Frontpage 2003 for features like layout tables, CSS, etc,
I don't use DRW at all for two reasons: 1) it imposes too strict limits on
what you can do and 2) it is too tamper-proof to my liking. Once you have
touched up some code in a DRW section, you can no longer open that file in
FP as the program will detect the changes and "repair the damage". On the
other hand, manual code lines written from scratch will be left untouched by
FP, although often the result is invisible in the WYSIWYG view. But anyway,
your best and most reliable page viewer will always remain your target
browser (IE for example). Of course for ASP pages to work on your local PC,
you need to have IIS (in W2K / XP Pro) or PWS (W98SE) installed and running.

So yes, my advice is to drop DRW all together and learn to hand code. I made
the move about six months ago, and it has been a very liberating experience.
But I still use FP for basic site management, tables, and style sheets.

If you are interested I might be able to assist you a bit further along the
way towards creating your DRW-free data-driven site.

Cheers,

TB

 

[Kathleen Anderson [MVP - FrontPage]]

no longer open that file in FP as the program will detect the changes
and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[TB]

True, but if one feels confident enough to try to modify FP-generated code,
why not take the next step and write your own? A trial-and-error process
playing with DRW could cost you more time than simply writing a couple of
lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

 

[Kathleen Anderson [MVP - FrontPage]]

It's a matter of finding the time, I think. When I get a request from a
user, it's always quicker for me to use the DRW then to take the time - at
that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[TB]

OK, I agree that there is an initial investment (of time) to make, but you
only make it once, because code is a very recycleable commodity. Believe me,
I am not a nerd in love with my PC, and at 40, I only decided to learn
something from scratch, because I could see a clear productivity gain,
allowing me the time to go for long walks in the mountains with my wife,
etc.

Cheers,

TB

 

[Michael Rothstein]

So far for what I've needed to do, I've been able to live within the world
of DRW. I'm still hoping for an answer to my original question: Can define a
variable in ASP and then use it in DRW?

Working directly with ASP to connect to my database has its obvious
advantages, however passing my variable from ASP to DRW would provide me
with an immediate solution. I've read some info on the web already regarding
ASP and database connections which I'll try to get working as I'm at a dead
end with my other possible solution. I appreciate your assistance and if I
get stumped, I may take you up on your offer.

Regards,

MR

 

[Michael Rothstein]

Yeah, that's where I'm at now. While learning ASP would be a good long term
investment, I was hoping for a 5 minute fix for something I may have
overlooked. Any idea if it is possible to use an ASP variable in DRW or is
learning ASP my only solution? I'm fine if learning ASP is the only way, but
I've found that I could make FrontPage do a lot more than I originally
thought with some help from the newsgroups and sites around the web.

MR

 

[Kathleen Anderson [MVP - FrontPage]]

I see in your first post that the variable is called myquery - where does
that come from and what does it look like?

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Yeah, that's where I'm at now. While learning ASP would be a good
long term investment, I was hoping for a 5 minute fix for something I
may have overlooked. Any idea if it is possible to use an ASP
variable in DRW or is learning ASP my only solution? I'm fine if
learning ASP is the only way, but I've found that I could make
FrontPage do a lot more than I originally thought with some help from
the newsgroups and sites around the web.

MR

It's a matter of finding the time, I think. When I get a request
from a user, it's always quicker for me to use the DRW then to take
the time - at that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

True, but if one feels confident enough to try to modify
FP-generated code, why not take the next step and write your own? A
trial-and-error process playing with DRW could cost you more time
than simply writing a couple of lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in message Once you have touched up some code in a DRW section, you can
no longer open that file in FP as the program will detect the
changes and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[TB]

The short answer is yes. Bearing in mind my initial advice of only using
your variable as the limiting argument, not the entire WHERE statement, in
the various dialogboxes of DRW you can always add a reference along the
lines of "<%=wherelimit%>" (without the quotation marks and DON'T FORGET the
equal sign). Make sure though that the variable is declared and populated
before the DRW code section on your page.

Cheers

TB

 

[Michael Rothstein]

The variable "myquery" completes a valid SQL statement. My original example
was a simplified version of what I'm trying to do. For testing, my ASP code
includes the following line:

myquery="(PartNum = '1234')"

and my DRW SQL code is:

SELECT * FROM Gifts WHERE ::myquery::

I thought it would be straight forward and the variable would be replaced. I
even created a form field on the page and have made the Intial Value to be:

<%Response.Write(myquery)%>

so that I can see that my variable was defined and displays, which it does.
However for the DRW results, I get the following error when instead I should
get my one record:

Database Results Error
Description: Syntax error in WHERE clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine

If I then define a default value for "myquery" to be:

(PartNum = '4567')

I DRW returns the default PartNum 4567 record to me.

So I know my query is right. Now if my variable would get replaced, I'd get
record 1234 returned rather than the default value which is being returned
instead of an error.

MR

I see in your first post that the variable is called myquery - where does
that come from and what does it look like?

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Yeah, that's where I'm at now. While learning ASP would be a good
long term investment, I was hoping for a 5 minute fix for something I
may have overlooked. Any idea if it is possible to use an ASP
variable in DRW or is learning ASP my only solution? I'm fine if
learning ASP is the only way, but I've found that I could make
FrontPage do a lot more than I originally thought with some help from
the newsgroups and sites around the web.

MR

It's a matter of finding the time, I think. When I get a request
from a user, it's always quicker for me to use the DRW then to take
the time - at that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


True, but if one feels confident enough to try to modify
FP-generated code, why not take the next step and write your own? A
trial-and-error process playing with DRW could cost you more time
than simply writing a couple of lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in message Once you have touched up some code in a DRW section, you can
no longer open that file in FP as the program will detect the
changes and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[Thomas A. Rowe]

Is there reason to have the field name as part of the variable?

If you want to use different fields in the query try use two variables.

MyField = "PartNum"
MyQuery = "1234"

SQL = "SELECT * FROM Gifts WHERE '" & MyField & "' = '" & MyQuery & "' "

The how I would do this via handcoding

You can see what is happening with your query by doing:

Response.Write SQL

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

The variable "myquery" completes a valid SQL statement. My original example was a simplified
version of what I'm trying to do. For testing, my ASP code includes the following line:

myquery="(PartNum = '1234')"

and my DRW SQL code is:

SELECT * FROM Gifts WHERE ::myquery::

I thought it would be straight forward and the variable would be replaced. I even created a form
field on the page and have made the Intial Value to be:

<%Response.Write(myquery)%>

so that I can see that my variable was defined and displays, which it does. However for the DRW
results, I get the following error when instead I should get my one record:

Database Results Error
Description: Syntax error in WHERE clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine

If I then define a default value for "myquery" to be:

(PartNum = '4567')

I DRW returns the default PartNum 4567 record to me.

So I know my query is right. Now if my variable would get replaced, I'd get record 1234 returned
rather than the default value which is being returned instead of an error.

MR

I see in your first post that the variable is called myquery - where does
that come from and what does it look like?

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

Yeah, that's where I'm at now. While learning ASP would be a good
long term investment, I was hoping for a 5 minute fix for something I
may have overlooked. Any idea if it is possible to use an ASP
variable in DRW or is learning ASP my only solution? I'm fine if
learning ASP is the only way, but I've found that I could make
FrontPage do a lot more than I originally thought with some help from
the newsgroups and sites around the web.

MR

in message It's a matter of finding the time, I think. When I get a request
from a user, it's always quicker for me to use the DRW then to take
the time - at that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


True, but if one feels confident enough to try to modify
FP-generated code, why not take the next step and write your own? A
trial-and-error process playing with DRW could cost you more time
than simply writing a couple of lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in message Once you have touched up some code in a DRW section, you can
no longer open that file in FP as the program will detect the
changes and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[Michael Rothstein]

My first goal is to establish whether I can pass an ASP variable to the DRW
SQL. The code I've listed here isn't my final code, but just a simple
example in hopes of getting it working. Once it works, then I'll be able to
move forward and code it properly.

Whether my code is optimized or not, I can't for the life of me figure out
why my variable isn't getting replaced by the value I've assigned to it.

In the past, I've successfully used variables in the DRW SQL statement which
come from form field dropdown boxes. This process was recommended to me here
in the newgroups.For instance, here is one of the queries I've used for
years which has been working fine:

SELECT * FROM Gifts where ::Category:: AND ::Model:: AND Published = 1 ORDER
BY Title ASC

"Category" and "Model" are names of dropdown boxes and the values get
replaced by values selected by the user when selecting an item in the
dropdown. The difference now is that I'm trying to use ASP variables rather
than the names of form fields. I didn't think that would make a difference,
but apparently it is.

If I can't get ASP and DRW working together in the way I need, I may end up
having to code this all by hand in ASP, but I thought I'd give it a try
since I'm familiar with DRW and the way in which it establishes a connection
with my database.

MR

Is there reason to have the field name as part of the variable?

If you want to use different fields in the query try use two variables.

MyField = "PartNum"
MyQuery = "1234"

SQL = "SELECT * FROM Gifts WHERE '" & MyField & "' = '" & MyQuery & "' "

The how I would do this via handcoding

You can see what is happening with your query by doing:

Response.Write SQL

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

The variable "myquery" completes a valid SQL statement. My original
example was a simplified version of what I'm trying to do. For testing,
my ASP code includes the following line:

myquery="(PartNum = '1234')"

and my DRW SQL code is:

SELECT * FROM Gifts WHERE ::myquery::

I thought it would be straight forward and the variable would be
replaced. I even created a form field on the page and have made the
Intial Value to be:

<%Response.Write(myquery)%>

so that I can see that my variable was defined and displays, which it
does. However for the DRW results, I get the following error when instead
I should get my one record:

Database Results Error
Description: Syntax error in WHERE clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine

If I then define a default value for "myquery" to be:

(PartNum = '4567')

I DRW returns the default PartNum 4567 record to me.

So I know my query is right. Now if my variable would get replaced, I'd
get record 1234 returned rather than the default value which is being
returned instead of an error.

MR

I see in your first post that the variable is called myquery - where does
that come from and what does it look like?

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


Yeah, that's where I'm at now. While learning ASP would be a good
long term investment, I was hoping for a 5 minute fix for something I
may have overlooked. Any idea if it is possible to use an ASP
variable in DRW or is learning ASP my only solution? I'm fine if
learning ASP is the only way, but I've found that I could make
FrontPage do a lot more than I originally thought with some help from
the newsgroups and sites around the web.

MR

in message It's a matter of finding the time, I think. When I get a request
from a user, it's always quicker for me to use the DRW then to take
the time - at that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


True, but if one feels confident enough to try to modify
FP-generated code, why not take the next step and write your own? A
trial-and-error process playing with DRW could cost you more time
than simply writing a couple of lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in message Once you have touched up some code in a DRW section, you can
no longer open that file in FP as the program will detect the
changes and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[TB]

As I have mentioned in another subthread, you can always add a reference
along the lines of "<%=wherelimit%>" (without the quotation marks and DON'T
FORGET the equal sign). Make sure though that the variable is declared and
populated before the DRW code section on your page. I hope you will bear
with me, if I here repeat my advice only using your variable to contain the
limiting argument, not the entire WHERE statement.

Cheers

TB

My first goal is to establish whether I can pass an ASP variable to the
DRW SQL. The code I've listed here isn't my final code, but just a simple
example in hopes of getting it working. Once it works, then I'll be able
to move forward and code it properly.

Whether my code is optimized or not, I can't for the life of me figure out
why my variable isn't getting replaced by the value I've assigned to it.

In the past, I've successfully used variables in the DRW SQL statement
which come from form field dropdown boxes. This process was recommended to
me here in the newgroups.For instance, here is one of the queries I've
used for years which has been working fine:

SELECT * FROM Gifts where ::Category:: AND ::Model:: AND Published = 1
ORDER BY Title ASC

"Category" and "Model" are names of dropdown boxes and the values get
replaced by values selected by the user when selecting an item in the
dropdown. The difference now is that I'm trying to use ASP variables
rather than the names of form fields. I didn't think that would make a
difference, but apparently it is.

If I can't get ASP and DRW working together in the way I need, I may end
up having to code this all by hand in ASP, but I thought I'd give it a try
since I'm familiar with DRW and the way in which it establishes a
connection with my database.

MR

Is there reason to have the field name as part of the variable?

If you want to use different fields in the query try use two variables.

MyField = "PartNum"
MyQuery = "1234"

SQL = "SELECT * FROM Gifts WHERE '" & MyField & "' = '" & MyQuery & "' "

The how I would do this via handcoding

You can see what is happening with your query by doing:

Response.Write SQL

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

The variable "myquery" completes a valid SQL statement. My original
example was a simplified version of what I'm trying to do. For testing,
my ASP code includes the following line:

myquery="(PartNum = '1234')"

and my DRW SQL code is:

SELECT * FROM Gifts WHERE ::myquery::

I thought it would be straight forward and the variable would be
replaced. I even created a form field on the page and have made the
Intial Value to be:

<%Response.Write(myquery)%>

so that I can see that my variable was defined and displays, which it
does. However for the DRW results, I get the following error when
instead I should get my one record:

Database Results Error
Description: Syntax error in WHERE clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine

If I then define a default value for "myquery" to be:

(PartNum = '4567')

I DRW returns the default PartNum 4567 record to me.

So I know my query is right. Now if my variable would get replaced, I'd
get record 1234 returned rather than the default value which is being
returned instead of an error.

MR


message I see in your first post that the variable is called myquery - where
does
that come from and what does it look like?

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


Yeah, that's where I'm at now. While learning ASP would be a good
long term investment, I was hoping for a 5 minute fix for something I
may have overlooked. Any idea if it is possible to use an ASP
variable in DRW or is learning ASP my only solution? I'm fine if
learning ASP is the only way, but I've found that I could make
FrontPage do a lot more than I originally thought with some help from
the newsgroups and sites around the web.

MR

in message It's a matter of finding the time, I think. When I get a request
from a user, it's always quicker for me to use the DRW then to take
the time - at that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


True, but if one feels confident enough to try to modify
FP-generated code, why not take the next step and write your own? A
trial-and-error process playing with DRW could cost you more time
than simply writing a couple of lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in message Once you have touched up some code in a DRW section, you can
no longer open that file in FP as the program will detect the
changes and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx

 

[Michael Rothstein]

Presumably I can't enter "<%=wherelimit%>" into the "Custom Query" dialog
box of the DRW wizard? That's the spot where I'm attempting to use my ASP
variable. But I think instead you're asking me to place "<%=wherelimit%>"
between the yellow DRW markers on my webpage, correct?

MR

As I have mentioned in another subthread, you can always add a reference
along the lines of "<%=wherelimit%>" (without the quotation marks and
DON'T FORGET the equal sign). Make sure though that the variable is
declared and populated before the DRW code section on your page. I hope
you will bear with me, if I here repeat my advice only using your variable
to contain the limiting argument, not the entire WHERE statement.

Cheers

TB

My first goal is to establish whether I can pass an ASP variable to the
DRW SQL. The code I've listed here isn't my final code, but just a simple
example in hopes of getting it working. Once it works, then I'll be able
to move forward and code it properly.

Whether my code is optimized or not, I can't for the life of me figure
out why my variable isn't getting replaced by the value I've assigned to
it.

In the past, I've successfully used variables in the DRW SQL statement
which come from form field dropdown boxes. This process was recommended
to me here in the newgroups.For instance, here is one of the queries I've
used for years which has been working fine:

SELECT * FROM Gifts where ::Category:: AND ::Model:: AND Published = 1
ORDER BY Title ASC

"Category" and "Model" are names of dropdown boxes and the values get
replaced by values selected by the user when selecting an item in the
dropdown. The difference now is that I'm trying to use ASP variables
rather than the names of form fields. I didn't think that would make a
difference, but apparently it is.

If I can't get ASP and DRW working together in the way I need, I may end
up having to code this all by hand in ASP, but I thought I'd give it a
try since I'm familiar with DRW and the way in which it establishes a
connection with my database.

MR

Is there reason to have the field name as part of the variable?

If you want to use different fields in the query try use two variables.

MyField = "PartNum"
MyQuery = "1234"

SQL = "SELECT * FROM Gifts WHERE '" & MyField & "' = '" & MyQuery & "' "

The how I would do this via handcoding

You can see what is happening with your query by doing:

Response.Write SQL

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

The variable "myquery" completes a valid SQL statement. My original
example was a simplified version of what I'm trying to do. For testing,
my ASP code includes the following line:

myquery="(PartNum = '1234')"

and my DRW SQL code is:

SELECT * FROM Gifts WHERE ::myquery::

I thought it would be straight forward and the variable would be
replaced. I even created a form field on the page and have made the
Intial Value to be:

<%Response.Write(myquery)%>

so that I can see that my variable was defined and displays, which it
does. However for the DRW results, I get the following error when
instead I should get my one record:

Database Results Error
Description: Syntax error in WHERE clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine

If I then define a default value for "myquery" to be:

(PartNum = '4567')

I DRW returns the default PartNum 4567 record to me.

So I know my query is right. Now if my variable would get replaced, I'd
get record 1234 returned rather than the default value which is being
returned instead of an error.

MR


in message I see in your first post that the variable is called myquery - where
does
that come from and what does it look like?

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


Yeah, that's where I'm at now. While learning ASP would be a good
long term investment, I was hoping for a 5 minute fix for something I
may have overlooked. Any idea if it is possible to use an ASP
variable in DRW or is learning ASP my only solution? I'm fine if
learning ASP is the only way, but I've found that I could make
FrontPage do a lot more than I originally thought with some help from
the newsgroups and sites around the web.

MR

in message It's a matter of finding the time, I think. When I get a request
from a user, it's always quicker for me to use the DRW then to take
the time - at that point in time - to learn ASP.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx


True, but if one feels confident enough to try to modify
FP-generated code, why not take the next step and write your own? A
trial-and-error process playing with DRW could cost you more time
than simply writing a couple of lines of code.

I don't claim to able to provide definite answers, only opinions...

TB

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in message Once you have touched up some code in a DRW section, you can
no longer open that file in FP as the program will detect the
changes and "repair the damage".

If that happens, it means you changed the code in the wrong place.

--

~ Kathleen Anderson
Microsoft MVP - FrontPage
Spider Web Woman Designs
web: http://www.spiderwebwoman.com/resources/
blog: http://msmvps.com/spiderwebwoman/category/321.aspx