We have a work order system on an NT Server (4.0) using FileMaker 6.0v4. People can go on the web and request a work order. Some work orders require an account #. We have two areas where you put your account# into. People in one area do not use the text box from the other area to put in the account #. After someone puts in the account for one particular area, a service rep can not see the account # unless the click into it and delete the return. If it is not done... the account is not charged.

I know why this happens. Both accounts fields on the web form reference one single field in the database (billable_to is the name). If one group enters their account first it is not a problem because that group is first on the web page, so the line/carriage return is below their account #. The other group is the problem. The initial value for the field is value="", input type ="text" and the class="mainform1" (The form where the account is sometimes "hidden"). My question is the best way to avoid this problem. Do you do something at the web page to prevent a "carriage return" from being imported from the web? Do you use validation or REPLACE with a calculation. We really do not want to do a seperate field for each group for other reasons. How can we either get one value into this field (since the web submittal is either/or), or delete the carriage upon import from the web? We can use web-based validation to prevent someone from entering values into both fields, but what about that darn carriage return? Sorry about the detail, just wanted to get all the info in. Thanks.

Substitute(billable_to;

I tried it using that function but the RECORDS...REPLACE command with calculated result does not let me use that formula. The default syntax for Substitute uses commas. I tried Substitute(billable_to,

Put the

OK... works fine. Thanks. However, this only replaces the current records the have the carriage return. When somebody submits later using the web form, the same problem occurs. How can I have it so everytime that form is submitted, the field in FM Pro does not get the carriage return. Again, this happens because two fields on the web form input to a single field in FM Pro. Only one field should get inputed data (so we really don't need two fields in FM Pro). We just need a way for the form to stop inputing the carriage return. Thanks.

You can do this using a Script, thereby eliminating the necessity to manually type it each time. Or, create a new field, make it a calculation, and the calculation can be as you used in the Replace.

HTH

Lee