I fill-out the form, putting the following in the References textarea,<br><br>(:togglehide image showtext="Show Floor Plan" hidetext="Hide image":)<br><br>LFOA Floor Plan<br><br>(:div id=image style="display:none":)<br>
<br>Attach:Systems/lfoaflpln.jpg<br><br>(:divend:)<br><br>I hit enter, and the form displays this in References--<br>(:togglehide image showtext="Show Floor Plan" hidetext="Hide image"<br><br>and then under the Projects link (outside the Fox form), I get-- <br>
LFOA Floor Plan<br><br>:)<br><br>LFOA Floor Plan<br>
<br>
:)<br><br>Thanks<br><br><div class="gmail_quote">On Thu, Jun 12, 2008 at 1:41 PM, Hans <<a href="mailto:design5@softflow.co.uk">design5@softflow.co.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Thursday, June 12, 2008, 6:17:42 PM, Scott Smith wrote:<br>
<br>
> Sorry about the partial. I didn't know if putting the full form in an email<br>
> would be bad form, like using all caps.<br>
<br>
</div>The tricky part is to provide a minimum on information, but have all<br>
relevant details intact. For a form problem this may mean to try to<br>
reduce the form to just the elements necessary to show the problem,<br>
but leave out unnecessary form elements, repetitions etc.<br>
This can save a lot of time for someone trying to help, and may also<br>
provide you with useful insight by narrowing down the problem.<br>
<br>
I often have problem in having to guess someones intentions/actions<br>
when they state a problem, because of a lack of detail given.<br>
But too much detail can be overwelming and off-putting.<br>
<br>
The best is often to get a url to look at, with access to the wiki source<br>
code (without that it is really frustrating). I don't find it<br>
necessary to have 'edit' access to a page, but 'source' access is<br>
vital.<br>
<font color="#888888"><br>
~Hans<br>
<br>
</font></blockquote></div><br>