stumped on a form

  • Thread starter Thread starter Jay Murray
  • Start date Start date
J

Jay Murray

Forgive any language differences here, I am only just
beginning to learn FP. Plain HTML in notepad has always
worked for me till now. :)

I have an ASP page attached to a access MDB.

User A fills out the form and submits it. All is fine here.

User B opens the results, surveys the results from user A
and fills in the needed fields.

One of these is a scrolling text box. They are able to
submit as much text in the box as they wish.

Here again all is fine EXCEPT, FP (or IIS) seems to be
truncating some of the response from User B.
The length of the response from user B seems to be random
but always short. Less than 2-3 sentences.

User A can fit pages into the first text box. But User B
can only save a few sentences.

In the DB it's self. The text is not saved.

Is this a known problem or am I just futzing something up?

Thanks for and direction I can look to resolving this!
 
-----Original Message-----
Forgive any language differences here, I am only just
beginning to learn FP. Plain HTML in notepad has always
worked for me till now. :)

I have an ASP page attached to a access MDB.

User A fills out the form and submits it. All is fine
here.

How are you doing this? For example:

o Are you configuring the Form Properties dialog box to
save results to a Database?
o Did you write your own ASP or ASP.NET code?
User B opens the results, surveys the results from user
A and fills in the needed fields.

Again, how are you doing this?
One of these is a scrolling text box. They are able to
submit as much text in the box as they wish.

Here again all is fine EXCEPT, FP (or IIS) seems to be
truncating some of the response from User B.
The length of the response from user B seems to be
random but always short. Less than 2-3 sentences.

User A can fit pages into the first text box. But User B
can only save a few sentences.

In the DB it's self. The text is not saved.

Without knowing how you implemented each page, I really
can't answer this.

The FrontPage "Save Results to Database" feature does
sometimes truncate data from text area boxes.

Also, when you open a table in Access and view a "memo"
field, Access only displays data up to the first line
ending, even if more data is present.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
|| Microsoft FrontPage Version 2002 Inside Out
|| Web Database Development Step by Step .NET Edition
|| Troubleshooting Microsoft FrontPage 2002
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
 
Thanks for the reply!

Some things I neglected to mention. This is on a intranet.
And Im using FP 2000.
If it makes any diffrence.
How are you doing this? For example:

o Are you configuring the Form Properties dialog box to
save results to a Database?


Yes, This this part is just simple. "Send to database"
radio button.

o Did you write your own ASP or ASP.NET code?

God no, not yet :)

Again, how are you doing this?

I use a search list to find the entries. the "ID" field
has this snipit
of code on the URL to pull up the item to be edited.

[URL HERE]?ID=<%=FP_FieldURL(fp_rs,"ID")%>

This brings up the item to be edited.
(BTW, the fields that are to be edited are at this point
blank. None of the information previously entered is
changed.)

This for is saved and the "Send to other" radio button
checked. calling a 3rd URL with POST.
*my head hurt at his point figuring this out*

the 3rd page uses this int he "Custom query" area.

update results
set Assigned_to='::Assigned_to::',
Problem_Resolution='::Problem_Resolution::'


All done. And it works. mostly.

If there is a better / easier (not as noobish) way please
let me know.


Without knowing how you implemented each page, I really
can't answer this.

The FrontPage "Save Results to Database" feature does
sometimes truncate data from text area boxes.


Is there a fix or work around for this?


Also, when you open a table in Access and view a "memo"
field, Access only displays data up to the first line
ending, even if more data is present.

Well that's just an extra kick in the pants....

Thanks again for the help!
 
Back
Top