Autodesk GIS Design Server
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
*Mena, Antoni
Same Element updated in two versions
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
84 Views, 2 Replies
10-03-2002 03:37 PM
Hi,
We are trying to update one element in more than one version at the same
time:
- we create element A in the top version
- we create and enter a version V1
- we update element A
- we create and enter a version V2
- we update element A
If we try this with the Generic Application, we realize that its behaviour
by default is to lock any updated element, so it is not allowed to modify
the element in a second version.
If we try this after changing the locking strategy for projects to "none",
the element should be ready to be updated in both versions, but when we try
to update it in a second version a new error arises "macro
'sare/ltr/Locking/BulkExtract/lock_data': 106 : DO: macro
'sare/ltr/Locking/BulkExtract/lock_data': 1 : syntax error : 'syntax error'
in for clause of select command". That error seems to show that the LTR API
is prepared for locking elements when updating.
The documentation is obscure in this point and we don't know how to
implement this.
Has anyone found and solved this problem?
We have also tried with Multi Branch Versioning but our DB seems not to be
prepared for Scenario use, and we haven't find how to set the tables up for
Scenario use along the documentation.
Does anyone know how to set up the DB for MBV support?
Thank-you,
Antoni Mena.
We are trying to update one element in more than one version at the same
time:
- we create element A in the top version
- we create and enter a version V1
- we update element A
- we create and enter a version V2
- we update element A
If we try this with the Generic Application, we realize that its behaviour
by default is to lock any updated element, so it is not allowed to modify
the element in a second version.
If we try this after changing the locking strategy for projects to "none",
the element should be ready to be updated in both versions, but when we try
to update it in a second version a new error arises "macro
'sare/ltr/Locking/BulkExtract/lock_data': 106 : DO: macro
'sare/ltr/Locking/BulkExtract/lock_data': 1 : syntax error : 'syntax error'
in for clause of select command". That error seems to show that the LTR API
is prepared for locking elements when updating.
The documentation is obscure in this point and we don't know how to
implement this.
Has anyone found and solved this problem?
We have also tried with Multi Branch Versioning but our DB seems not to be
prepared for Scenario use, and we haven't find how to set the tables up for
Scenario use along the documentation.
Does anyone know how to set up the DB for MBV support?
Thank-you,
Antoni Mena.
Re: Same Element updated in two versions
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-11-2002 08:33 AM in reply to:
*Mena, Antoni
Hi,
If you want to enable Multi-barnch Versioning, try reading the guide "Installing on Windows 2000" on the AGDS 8.0 documentation set. Take a look at chapter 4, Post-Instalation, e you'll find an item named "Enabling SUpport for Multi-Branch Versioning" or something like that.
But I'm not sure if the Generic application supports MBV...
Please let me know if you have success in using GenApp with MBV, that you interest me...
Hope this helps.
Fabio
If you want to enable Multi-barnch Versioning, try reading the guide "Installing on Windows 2000" on the AGDS 8.0 documentation set. Take a look at chapter 4, Post-Instalation, e you'll find an item named "Enabling SUpport for Multi-Branch Versioning" or something like that.
But I'm not sure if the Generic application supports MBV...
Please let me know if you have success in using GenApp with MBV, that you interest me...
Hope this helps.
Fabio
*Mena, Antoni
Re:
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-11-2002 05:11 PM in reply to:
*Mena, Antoni
Hi Fabio,
we have succeed in enabling the database for MBV.
You only have to run a script as described in the documentation as you said.
But, anyway, it doesn't allow updating an element in two independent
versions; so we doesn't make use of MBV.
As long as we know GenApp was developed without MBV in mind. So surely
you will find lots of problems. We have already found one: the method
CVersionManager::getSelectionSet
in the service AeCsQueryService doesn't work properly for MBV.
Good luck with MBV.
we have succeed in enabling the database for MBV.
You only have to run a script as described in the documentation as you said.
But, anyway, it doesn't allow updating an element in two independent
versions; so we doesn't make use of MBV.
As long as we know GenApp was developed without MBV in mind. So surely
you will find lots of problems. We have already found one: the method
CVersionManager::getSelectionSet
in the service AeCsQueryService doesn't work properly for MBV.
Good luck with MBV.
