Oops, so embarrassing! I didn't mean to send this to all of OzMoss
sorry. You must agree though. Thanks a lot Clayton for being active on
this list. I'm a bit biased though as we work together J
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Mark Daunt
Sent: Thursday, 20
Any one have any ideas.
All content seems to be there just not accessible because of versions in
database table differ.
I know this sounds simplistic but can I just add database version
directly to table.
Regards
Peter M.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
The first thing I would try is creating a new site, and attaching one of
the databases to it. I would also back up, and the restore a databasse,
and sue that for trying to fix the problem ,rather than using a current
content database
Cheers
Craig
-Original Message-
From: [EMAIL
Thanks for the reply!
That was the basis of Ishai's reply, which I would like to avoid as
this feature otherwise has no code. It seems a bit crap that you'd
have to add code for something as simple as a dependancy when
dependancies are built into SP to begin with.
On 12/20/07, Clayton James
Thanks Clayton.
Luckily you can use the same form for your association and
initialisation. Change the workflow.xml Association_FormURN and
Instantiation_FormURN to use the same urn id.
If I use the same form, what is the best approach to hide and show the
relevant fields? ie. If it's the
