ASP.NET and FP 2003.... Continued

[Frank Smith]

Ok on the advice from "spiderwoman" and "Cowboy" I installed FP2003 and got
the SP2 update.
(All this to rebuild one mis-behaving ASP form.)

I started a new ASP.NET DBR form and pasted in my Query from the form that
had been working fine for years until two weeks ago.
UPDATE schedule SET xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

The Wizard now says there is an Error in the above code.
So after trying some research on the MS KB and coming up empty I started
playing with the SQL

IF I delete ALL the fields EXCEPT One and keep the WHERE it checks out fine.
UPDATE schedule SET xdate='::xdate::' WHERE (xrecnbr=::xrecnbr:

Is there a new syntax in 2003 for multiple fields to update??
Frank

 

[Frank]

In looking further....
UPDATE schedule SET xdate='::xdate::',dispatcher='::dispatcher::' WHERE
(xrecnbr=::xrecnbr:
Does NOT Validate - added the second field update with a variable.

UPDATE schedule SET xdate='::xdate::',dispatcher='1234' WHERE
(xrecnbr=::xrecnbr:
DOES Validate, note the second field is set to a constant value.

Set constants for the remaining fields values and the whole string
Validated.
Back in the "old days" I wrote a lot of SQL statements in MS Visual
FoxPro and never seen anything like this.

Hope you MVP's have a clue,
Frank

 

[Kathleen Anderson [MVP - FrontPage]]

Inline.

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

Ok on the advice from "spiderwoman" and "Cowboy" I installed FP2003 and
got
the SP2 update.
(All this to rebuild one mis-behaving ASP form.)

I started a new ASP.NET DBR form and pasted in my Query from the form that
had been working fine for years until two weeks ago.

Did you create a new web or just a new form within an existing web?

UPDATE schedule SET xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

Looks fine to me.

The Wizard now says there is an Error in the above code.

What is the exact text of the error message?

 

[Frank Smith]

Went about it two ways:
1. Opened the old ASP form and selected ASP.NET and never go past the
Query.
2. Started a new ASP.NET form and when I got to the Custom Query pasted in
the code below
Both in the existing web.
Development is done on my system and then Published when I have all the bugs
out.

Went to another DBR in my web where the UPDATE basically blanks all the
fields and stuffs a future date in one field.
Works fine - seems that stuffing constants works but the Variables have a
problem.

 

[Kathleen Anderson [MVP - FrontPage]]

Inline.

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

Went about it two ways:
1. Opened the old ASP form and selected ASP.NET and never go past the
Query.
2. Started a new ASP.NET form and when I got to the Custom Query pasted
in
the code below

What happens if you try ASP instead of ASP.Net?

Both in the existing web.

I found a new KB article yesterday that talks about how to correct errors in
existing DRWs after you apply Office 2003 SP-2:
http://support.microsoft.com/default.aspx?scid=kb;en-us;907307

 

[Frank Smith]

ASP vs ASP.NET no change, same problem.
Give me a few days to get back home - KB Article you found hits "a few
nerves" and may do the trick - just Open and Save to rewrite the inc's.
After I try that, if I still have errors I will note the Exact Error msg.

 

[Frank Smith]

Well since one variable worked.... I created a new ASP.NET page and in the
DBR only used one variable, Validated fine.
Saved it to update all the .inc's
Reopened it and put in the full Custom DBR.... would NOT validate!!

The only error returned on Validation is a standard message box "The Custom
Query Contains Errors" -- no other details given.
UPDATE schedule SET xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

I sure cannot find any errors in this - and it is the same one that has been
working for years with FP2002.

 

[Kathleen Anderson [MVP - FrontPage]]

Frank:
How sensitive is the info in your database? Can you copy 10 or so records to
a new database and send it to me?

--

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

 

[Frank Smith]

For some reason msnews will not take a 200k attachment so I sent it to your
emailbox (e-mail address removed).

nothing sensitive in here, just the work schedule for a flying club.
To keep the db small I just recycle the records, blank out those over 30
days old and issue a new date field.

When I installed 2003 is there anything else that must be installed along
with it.... have not seen anything about that but thought I might ask as
this is weird.
Thanks for the interest,
Frank

 

[Kathleen Anderson [MVP - FrontPage]]

Frank:
I received the file - I will take a look at it when I get home.

--

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

For some reason msnews will not take a 200k attachment so I sent it to
your emailbox (e-mail address removed).

nothing sensitive in here, just the work schedule for a flying club.
To keep the db small I just recycle the records, blank out those over 30
days old and issue a new date field.

When I installed 2003 is there anything else that must be installed along
with it.... have not seen anything about that but thought I might ask as
this is weird.
Thanks for the interest,
Frank

Frank:
How sensitive is the info in your database? Can you copy 10 or so records
to
a new database and send it to me?

--

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

Well since one variable worked.... I created a new ASP.NET page and in
the
DBR only used one variable, Validated fine.
Saved it to update all the .inc's
Reopened it and put in the full Custom DBR.... would NOT validate!!

The only error returned on Validation is a standard message box "The
Custom Query Contains Errors" -- no other details given.
UPDATE schedule SET xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

I sure cannot find any errors in this - and it is the same one that has
been working for years with FP2002.




ASP vs ASP.NET no change, same problem.
Give me a few days to get back home - KB Article you found hits "a few
nerves" and may do the trick - just Open and Save to rewrite the inc's.
After I try that, if I still have errors I will note the Exact Error
msg.

in
message Inline.

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


Went about it two ways:
1. Opened the old ASP form and selected ASP.NET and never go past
the
Query.
2. Started a new ASP.NET form and when I got to the Custom Query
pasted
in
the code below

What happens if you try ASP instead of ASP.Net?

Both in the existing web.

I found a new KB article yesterday that talks about how to correct
errors
in
existing DRWs after you apply Office 2003 SP-2:
http://support.microsoft.com/default.aspx?scid=kb;en-us;907307


Development is done on my system and then Published when I have all
the
bugs
out.

Went to another DBR in my web where the UPDATE basically blanks all
the
fields and stuffs a future date in one field.
Works fine - seems that stuffing constants works but the Variables
have
a
problem.

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in
message Inline.

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


Ok on the advice from "spiderwoman" and "Cowboy" I installed
FP2003
and
got
the SP2 update.
(All this to rebuild one mis-behaving ASP form.)

I started a new ASP.NET DBR form and pasted in my Query from the
form
that
had been working fine for years until two weeks ago.

Did you create a new web or just a new form within an existing web?

UPDATE schedule SET
xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

Looks fine to me.

The Wizard now says there is an Error in the above code.

What is the exact text of the error message?

So after trying some research on the MS KB and coming up empty I
started
playing with the SQL

IF I delete ALL the fields EXCEPT One and keep the WHERE it
checks
out
fine.
UPDATE schedule SET xdate='::xdate::' WHERE (xrecnbr=::xrecnbr:

Is there a new syntax in 2003 for multiple fields to update??
Frank

 

[Kathleen Anderson [MVP - FrontPage]]

Frank:
It appears to me that the problem was not with the Database Interface
Wizard; it was with your database design. The field 'xrecnbr' needs to be
defined with a Data Type of Autonumber in Access and it should be the first
field in the table. I'm sending back a modified table that you can start
over with.

HTH,

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

Frank:
I received the file - I will take a look at it when I get home.

--

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

For some reason msnews will not take a 200k attachment so I sent it to
your emailbox (e-mail address removed).

nothing sensitive in here, just the work schedule for a flying club.
To keep the db small I just recycle the records, blank out those over 30
days old and issue a new date field.

When I installed 2003 is there anything else that must be installed along
with it.... have not seen anything about that but thought I might ask as
this is weird.
Thanks for the interest,
Frank

Frank:
How sensitive is the info in your database? Can you copy 10 or so
records
to
a new database and send it to me?

--

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




Well since one variable worked.... I created a new ASP.NET page and in
the
DBR only used one variable, Validated fine.
Saved it to update all the .inc's
Reopened it and put in the full Custom DBR.... would NOT validate!!

The only error returned on Validation is a standard message box "The
Custom Query Contains Errors" -- no other details given.
UPDATE schedule SET xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

I sure cannot find any errors in this - and it is the same one that has
been working for years with FP2002.




ASP vs ASP.NET no change, same problem.
Give me a few days to get back home - KB Article you found hits "a few
nerves" and may do the trick - just Open and Save to rewrite the
inc's.
After I try that, if I still have errors I will note the Exact Error
msg.

in
message Inline.

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


Went about it two ways:
1. Opened the old ASP form and selected ASP.NET and never go past
the
Query.
2. Started a new ASP.NET form and when I got to the Custom Query
pasted
in
the code below

What happens if you try ASP instead of ASP.Net?

Both in the existing web.

I found a new KB article yesterday that talks about how to correct
errors
in
existing DRWs after you apply Office 2003 SP-2:
http://support.microsoft.com/default.aspx?scid=kb;en-us;907307


Development is done on my system and then Published when I have all
the
bugs
out.

Went to another DBR in my web where the UPDATE basically blanks all
the
fields and stuffs a future date in one field.
Works fine - seems that stuffing constants works but the Variables
have
a
problem.

"Kathleen Anderson [MVP - FrontPage]" <[email protected]>
wrote
in
message Inline.

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


Ok on the advice from "spiderwoman" and "Cowboy" I installed
FP2003
and
got
the SP2 update.
(All this to rebuild one mis-behaving ASP form.)

I started a new ASP.NET DBR form and pasted in my Query from the
form
that
had been working fine for years until two weeks ago.

Did you create a new web or just a new form within an existing
web?

UPDATE schedule SET
xdate='::xdate::',dispatcher='::dispatcher::',
phone=':hone::',amcrew='::amcrew::',pmcrew=':mcrew::',
crew3='::crew3::',crew4='::crew4::',amtow='::amtow::',
pmtow=':mtow::',instructor='::instructor::',ipilot='::ipilot::',
instruct2='::instruct2::' WHERE (xrecnbr=::xrecnbr:

Looks fine to me.

The Wizard now says there is an Error in the above code.

What is the exact text of the error message?

So after trying some research on the MS KB and coming up empty I
started
playing with the SQL

IF I delete ALL the fields EXCEPT One and keep the WHERE it
checks
out
fine.
UPDATE schedule SET xdate='::xdate::' WHERE
(xrecnbr=::xrecnbr:

Is there a new syntax in 2003 for multiple fields to update??
Frank