Kaeli,
"kaeli" <tiny_one@NOSPAM.comcast.net> wrote in message
news:MPG.1b28f75493c3a004989eb7@nntp.lucent.com...[color=blue]
> In article <c9imhj$h05$1$8302bc10@news.demon.co.uk>,
>
mark@notmeyeardley.demon.co.uk enlightened us with...[color=green][color=darkred]
> > >[/color]
> >
> > No better, I'm afraid. Same result.
> >
> > Noo - we need to document.write(x) - it the outcome of the process![/color][/color]
'x'[color=blue][color=green]
> > is the string that writes out a set of 9 page HTML links each with[/color][/color]
an[color=blue][color=green]
> > onClick event which checks for unsubmitted current page items before
> > going to the next page. The script runs inline during page load so
> > nothings overwritten - code is old fashioned top-down code, i.e. not
> > using x/y positioned DIVs etc.
> >[/color]
>
> Ah, that makes more sense now.
>
> I think Matt nailed it for you. Did you get this fixed?
>
> --
> --
> ~kaeli~
> Well, aren't we just a flipping ray of sunshine?
>
http://www.ipwebdesign.net/wildAtHeart
>
http://www.ipwebdesign.net/kaelisSpace
>[/color]
Sorry, I figured this had run out of steam. I did solve the issue by
splitting the function in two - the bit with the object reference is now
in a JS library and the object required (one of a small number of form
names) is resolved there based on strings passed from the first,
dynamically written function. Not ideal as the form names are now hard
coded in the library function but this is one-off for someone else
who'll never touch the code. So, not ideal in many senses, but it works
and if fit for purpose in the context of use.
I was going to say all the suggestions failed but I realise I'd
misunderstood Matt's idea. I tried passing document.forms[formName] when
he mean passing formName and using it later as document.forms[formName].
Oh well, now I have 2 solutions <g>.
Thanks to all,
Mark