Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Default Values in DB Results Wizard 1
- Thread starter jezmondo
- Start date
-
1
- #2
At what point is the wizard requiring you add defaults? Are you using the DIW or DRW?
Tiffany
Microsoft MVP - FrontPage
Tiffany
Microsoft MVP - FrontPage
- Thread starter
- #3
I'm using DRW in FP2000. If I don't provide defaults values I get the following error
------------------------------------------
Database Results Error
Description: [Microsoft][ODBC Microsoft Access Driver] Data type mismatch in criteria expression.
Number: -2147217913 (0x80040E07)
Source: Microsoft OLE DB Provider for ODBC Drivers
One or more form fields were empty. You should provide default values for all form fields that are used in the query.
---------------------------------------------
This really does seem to seriously restrict the functionality of asp with Frontpage
------------------------------------------
Database Results Error
Description: [Microsoft][ODBC Microsoft Access Driver] Data type mismatch in criteria expression.
Number: -2147217913 (0x80040E07)
Source: Microsoft OLE DB Provider for ODBC Drivers
One or more form fields were empty. You should provide default values for all form fields that are used in the query.
---------------------------------------------
This really does seem to seriously restrict the functionality of asp with Frontpage
One thing you can do is open the Access Database and be sure that you set any fields you want to "Allow zero length" to Yes. By default it is usually set at no.
You also mentioned a problem with the date field. There is a known issue with the DRW and date fields. It is suggested that you could change your "date" field to a text box to work around the issue - or another solution is:
HTH
Tiffany
Microsoft MVP - FrontPage
You also mentioned a problem with the date field. There is a known issue with the DRW and date fields. It is suggested that you could change your "date" field to a text box to work around the issue - or another solution is:
HTH
Tiffany
Microsoft MVP - FrontPage
- Thread starter
- #5
Hi Tiffany
Thanks for your help. However I'm still needing to provide default values for all fields within the update. Even though the fields in my db are set to zero length and not required, Frontpage still insists on having a default!
I'll probably get round this by doing some whizzy stuff on the db side of things. Seems a real shame that Frontpage can't handle empty fields for updates though.
If you've got any other ideas they're more than welcome.
Thanks again
Jeremy
Thanks for your help. However I'm still needing to provide default values for all fields within the update. Even though the fields in my db are set to zero length and not required, Frontpage still insists on having a default!
I'll probably get round this by doing some whizzy stuff on the db side of things. Seems a real shame that Frontpage can't handle empty fields for updates though.
If you've got any other ideas they're more than welcome.
Thanks again
Jeremy
- Status
Similar threads
- Locked
- Question