FP Form Won't Submit (Store) Data Into MDB File... Please help! :-

[Cyburke]

Hello, I've seen this question asked many many times throughout my searches
but haven't come across a definitive answer as of yet. Hoping the MSDN
community can assist me.

Windows 2003 Server
FP Extensions are installed

My users have been trying desperately to create forms in FP that connect to
their MDB and store the results within. When you load the page, fill out the
form, and click submit; you get the "results submitted" window that confirms
the data was received. However, when you open the MDB file, no data is there.

I have checked the global.asa file and the appropriate connection string
information appears to be enclosed within. The connection to the DB is
verified properly through the Properties portion of FP as well.

Can anyone assist me? I will provide you with whatever information you need
as I am the administrator of the box itself.

Thank you very much for any and all assistance in resolving this matter.

 

[Chris Leeds, MVP-FrontPage]

can you right click the form, chose form properties and make sure they're
pointing it to the right .mdb and also make sure that you're looking in the
right .mdb when you browse.
It's happened to me more times that I'd like to admit where I'm looking in
the wrong place or FrontPage is.

--
Chris Leeds,
Microsoft MVP-FrontPage

If you make web sites for other people, you should check out ContentSeed:
http://contentseed.com/

 

[Stefan B Rusynko]

Verify the location of the .mdb (by default the fpdb folder w/i a FP web) has write permissions enabled on the server
- then have them check they can open the DB w/ a simple query before attempting to write to it

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Hello, I've seen this question asked many many times throughout my searches
| but haven't come across a definitive answer as of yet. Hoping the MSDN
| community can assist me.
|
| Windows 2003 Server
| FP Extensions are installed
|
| My users have been trying desperately to create forms in FP that connect to
| their MDB and store the results within. When you load the page, fill out the
| form, and click submit; you get the "results submitted" window that confirms
| the data was received. However, when you open the MDB file, no data is there.
|
| I have checked the global.asa file and the appropriate connection string
| information appears to be enclosed within. The connection to the DB is
| verified properly through the Properties portion of FP as well.
|
| Can anyone assist me? I will provide you with whatever information you need
| as I am the administrator of the box itself.
|
| Thank you very much for any and all assistance in resolving this matter.

 

[Cyburke]

location of the .mdb is verified - has write permissions

just created a FP .asp page that pulls the data from the .mdb using the
existing FP db connection onto the page. i inserted two records manually into
the .mdb through Access and the .asp page pulled those items onto the results
page.

verified again that no data is being written to the .mdb file when using an
..asp page through FP that is supposed to write to the db. verified twice.
also received the "form confirmation" screen (as i always do) after hitting
submit. no data written to the db.

thoughts, ideas?

 

[Thomas A. Rowe]

Make sure the root web or subweb is set as an application root under the home directory tab under
IIS MMC for the specific web site.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================