symbol not subsettable still problematic on simple nlmer call [SEC: UNCLASSIFIED]

Hi all,

I've done some testing this morning to see what is triggering my error "Error: object of type 'symbol' is not subsettable" and even running the simplest (incorrect form):
nlmer(RESPONSE ~ BOXCOXXY,
+ data=data0)

Produces the same error, suggesting the issue lies with the pass from the data frame into nlmer.

traceback() results are the same as yesterday, stopping at the same point:
5: notnull(x$formula)
4: formula.default(object, env = baseenv())
3: formula(object, env = baseenv())
2: as.formula(formula[[2]])
1: nlmer(RESPONSE ~ BOXCOXXY, data = data0)

I have tested data0 with is.data.frame(data0) and received the result TRUE just to make sure I hadn't done anything silly with the data frame construction.

I'm mystified to the underlying problem.

In case it helps, here is the result to objects()
[1] "Agegrp4Coeff" "Agegrp5Coeff" "Agegrp6Coeff" "Agegrp7Coeff" "Agegrp8Coeff" "data0"        "lambda_value" "parmsg2"      "parmsg2_gee"  "Race1Coeff"   "Race3Coeff"   "random2"      "Scale"        "SeqCoeff"     "WeekendCoeff"

And the result of search() is:
[1] ".GlobalEnv"        "package:lme4"      "package:Matrix"    "package:lattice"   "package:geepack"   "package:MASS"      "package:stats"     "package:graphics"  "package:grDevices" "package:utils"     "package:datasets"
[12] "package:methods"   "Autoloads"         "package:base"

I'm running 64-bit R 2.14.0 on a networked computer, accessing a server remotely via Vmware, in a Windows 7 environment.

Cheers
Michelle



UNCLASSIFIED

**********************************************************************
This email and any files transmitted with it are confide...{{dropped:12}}