Great, glad it's working.
The problem with these situations is that the actual cause of the error can be anywhere. It can be in the call to the function, in the function itself, in the way you're including the external file and so on.
That's why I asked you to post the final HTML so I can see what code ended up in the browser. Of course, with hindsight, posting only the code for the <head> section and the actual onclick call was more than enough to find the problem. But hey, once you know the solution, every problem is easy... ;)
I still get the error about the semi-colon, but I think this is caused by the same "public function" issue.
And I know what you mean by working alone and missing a second set of eyes. I have done that for a while (couple of years ago) and it isn't easy indeed. Then again, you have 50664 extra sets of eyes according to the homepage of P2P ;) (
http://p2p.wrox.com/default.asp)
Cheers and have a good weekend.
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of
ASP.NET 2.0 Instant Results and
Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.