I found the error, for anyone searching the archives.
The issue was that in my JSON, I had left out a comma!
A great way to debug this was to put my JSON definition of a fairly
complex data structure at the END of the javascript file. After that I
could see that the functions were fine, it was just an error in my
declaration. Pretty basic stuff, but it's exactly that kind of thing
which'll getcha
Steven
wrote:
> > > I just checked the page again to validate W3C validation, and it's
> > > fine, so IB think the language attribute is still kosher in this DTD.
> > >
> > > Steven
> > >
> >
> > Let me be the first to chastise you for top-posting 
> >
> > Perhaps the problem was an IE security-zone issue? If it works on the
> > new server and not the old, with no other changes (in file locations and
> > whatnot), I can't think of any other reason - except, perhaps, that the
> > old server was somehow mangling and / or mis-delivering your javascript
> > file.
>
> An eagle-eyed developer friend noticed this, in my JSON hash statement
> I had the line
>
> something_block : {
> "foo": "foot",
> "bar" "bart",
> }
>
> Can you spot the error? That's right, that last comma creates the
> message unhelpfully expressed by IE as "object expected".
>
> Whew! Things are working now!
>
> Steven