Fields empty error

[Moving rpts from Access to Rptg Services]

I'm using the details, edit and update pages created by DIW to retreive the
data from the forms I have created, make edits and save to the database.
When I hit the OK button on the Edit page after making changes to the form, I
receive this message:

Database Results Wizard Error
Description: No value given for one or more required parameters.
Number: -2147217904 (0x80040E10)
Source: Microsoft JET Database Engine
One or more form fields were empty. You should provide default values for
all form fields that are used in the query.

I've looked up the error and none of the fixes seem to work for me
1. one said to put brackets around the timestamp in the file - I don't have
timestamp noted in my code
2. one suggested the fields might be required and not filled in...the only
required field is the ID and it is already populated

I don't know where to go from here. Any ideas?

Thank you,

Karen

 

[Moving rpts from Access to Rptg Services]

I forgot to include that I am using a frame on the left with the location
code dropdown and links to the forms/surveys and an I-frame on the right to
display the results (first detail then edit and results.

 

[Nicholas Savalas - http://savalas.tv]

Dear Karen,
First, publish your entire site (including subwebs, if any) to a folder
on your computer. Then, throw the whole site out (please see
http://groups.google.com/group/micr...513bf38851e/4a57e28112aec456#4a57e28112aec456
) - including your existing database connections. I am not kidding.
Throw every folder out. Then, first, reimport your database (not to
the fpdb folder - to the root, FP will create the fpdb folder and ask
you to set it there, say yes) and when FP asks you if you would like to
create a new connection, say yes - and call the new database connection
something different than the first. When the wizard starts, it will ask
you what database you wish to connect to - choose to 'use existing
database' and go from there. Every web designer, sooner or later,
learns to hate his tools, and decides to learn the underlying
programming language. See you at http://asp.net - good luck.

 

[Moving rpts from Access to Rptg Services]

Nicholas, can you tell me what has happened and why and how this will solve
my issues?

Thank you,

Karen

 

[Nicholas Savalas - http://savalas.tv]

Dear Karen,
The DIW is OK for a very simple tasks, but when it comes to
sophisticated applications, or in situations where the original scope
of your design has changed or might change, the DIW is not the way to
go. It was the DIW that originally frustrated me so much that I began
to learn ASP code - the store that I bought FP 2000 from wouldn't take
it back and give me a refund, and my application was already up on the
web, and broken, just like yours.
1) The level that the page (the I-frame) that holds the database
results sits in your web often has to be at the same level as the DRW
originally made it. Sometimes this is true, and sometimes it is not.
Why? No one, not even the support team at Microsoft that I have spent
hours on the phone with, knows. The DIW is particularly unreliable in
sub webs.
2) Maybe, by accident, a field name was spelled incorrectly, or you
have customized it yourself, and given it an illegal name .
3) You tried to insert the wrong datatype - did you specify number when
you're imputting text? Are you trying to input date in a long form
when you originally specified short form?
3) Are you using those validation bots? If inserted specifying illegal
parameters, or often, though not always, if inserted into the DIW
submission page at all, the whole application crumbles like a house of
cards.
4) Does your editor page include all of the fields that your submission
form does? Does your submission form include all of the fields that
your editor page does? If not, one or more of the values was, indeed,
blank.
I do not have all the facts, therefore, I cannot give you the correct
answers. I will tell you this, though, I would get away from the DIW
for the editing part of your application, and instead use this:
http://www.codeproject.com/asp/ute.asp
Free, fully and simply explained, and exceptionally easy to install, I
know of more than a few pros who use this application rather than build
their own.
As far as the user form updating a database, while Microsoft has tried
to make it easy in FP, a comprehensive and fully explained solution is
available at:
http://www.webwizguide.info/asp/tutorials/add_to_database.asp
And, while I am not sure whether the folks at Microsoft will hate me or
love me for this, a very simple solution for displaying the results
from your database are given at:
http://www.webwizguide.info/asp/tutorials/connecting_to_a_database.asp
My advice to you is to use the DIW and DRW sparingly, if at all. ASP
code is fun, easy, is very quick to execute, and can be manipulated to
perform almost any task. Plus, you can design and build more
sophisticated solutions than you can now, and you can charge more money
from your clients because you will have gone from being a simple web
page maker to a professional solutions architect. Anyone can build a
web page; templates and web based site creators are free and
everywhere. An experienced architect of the Internet solutions - a
person who can see a need, design, and build it, are in extremely high
demand. I sense that you could easily become one of those people. I
hope I have been of some help. Please post here if you're still having
problems; I, and many others, will be most glad to help you. Good
luck, Karen.

 

[Moving rpts from Access to Rptg Services]

at least you have given me hope. I will go to the links you have suggested.
Unfortunately, the timing for me to get these forms available is immediate so
truly learning ASP will be a future task. Thanks again for your time and
advice...off I go again : )

 

[Kevin Spencer]

Just an additional note: I used FrontPage for a good number of years, to
develop ASP pages. As ASP pages use an HTML template (the .asp page),
FrontPage provides nice tools for quickly generating the HTML needed in the
page. The ASP code must, of course, be written by hand, but FrontPage does
provide some intellisense, and is ASP-friendly.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition

 

[Moving rpts from Access to Rptg Services]

Ok, thank you Kevin for the info!

Just an additional note: I used FrontPage for a good number of years, to
develop ASP pages. As ASP pages use an HTML template (the .asp page),
FrontPage provides nice tools for quickly generating the HTML needed in the
page. The ASP code must, of course, be written by hand, but FrontPage does
provide some intellisense, and is ASP-friendly.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition