The /wrkgrp parm has reasonably had to be embedded in the command line ever
since Access2000 and earlier, so you're talking of two different things:
-embedding /wrkgrp in command-line is standard practise since A97 or A2.0.
-A2007 only supports workgroups (ULS) as a legacy concession (meaning it's
still implemented but not available for "new" apps or no-doubt not for
modifications such as the Workgroup Administrator.
It won't be added to any final release (my understanding, MS have already
decided to obsolete ULS and workgroups). This means, if you want to use ULS,
you have to write your program in a previous version of Access, and A2007
might then deem to run it. I expect you would need to maintain it via an older
version.
If you run ULS or workgroups in Access2007, you are running in LEGACY MODE.
Given MS quite good history of legacy compatibility, and the extensive
implementation of ULS, this could be so for quite some time. It's just (I
imagine) you can't modify it with A2007.
(Have I expressed this right?)
(personally I think the removal of ULS for new apps sucks. It's as though, one
of my customers complained invoicing on my app was too difficult, so I said
"Easy...I'll just remove the invoicing!"
![Smile :-) :-)](/styles/default/custom/smilies/smile.gif)
)
Chris
I haven't finished. I refused to implement A2003 because of the licensing
stuff (let alone whether it had usefull advancements). Now I refuse to
consider A2007 because it removes basic required functionality/or intends to.
What is MS playing at? They already know that, if developers don't like a new
Access, they are quite capable of keeping old versions going for 10yrs or
more. And developers have more influence (by no means total) on customers than
MS may think.