• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Version Maintenance in Xe

We are currently upgrading from B7322 to Xe. My question is how to maintain
Versions in Xe. I have been playing with the Xe Demo and created some
Versions. They all seem to default into the Demo Project (if another
project isn't in focus)in OMW. That works for me since I'm the Developer
and can drag them down to the correct Project or move them over to OL. What
happens when end-users create Versions? Does this mean every time an
end-user creates a Version I have to move them out of the Demo project since
they don't have access to OMW?????

TIA

Richard

B7322 SP 12.2 AS400 SQL 6.5 moving to Xe!!!
 

Zoltan_Gyimesi

Legendary Poster
Richard,

Good issue.
Unfortunatley the situation is a bit complicated.
For all User Profile when you create them, automatically will be created a DEFAULT project for that user (Not DEMO).
If a user creates a new version outside of OMW then it will be placed into her/his DEFAULT project.

If you want to manipulate others' DEFAULt project then you have to be added to these DEFAULT projects with an approriate User Role.

An other solution could be to configure your Object Management with limited rights for the mentioned users and teach them to use OMW.

I know, the best choice sometimes is not a good choice.

Regards,
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 

CHo

VIP Member
Prior to Xe, to do bulk transfer of versions you would run R9830512. Does that mean if I need to transfer user's version from one pathcode to another one that I would need to manipulate people's default projects on a massive scale? Does R9830512 work in Xe?

Catherine Ho
Programmer/Analyst
Dundee Realty
Toronto, ON
Canada
416-365-5999 ext. 8805

Richard,

Good issue.
Unfortunatley the situation is a bit complicated.
For all User Profile when you create them, automatically will be created a DEFAULT project for that user (Not DEMO).
If a user creates a new version outside of OMW then it will be placed into her/his DEFAULT project.

If you want to manipulate others' DEFAULt project then you have to be added to these DEFAULT projects with an approriate User Role.

An other solution could be to configure your Object Management with limited rights for the mentioned users and teach them to use OMW.

I know, the best choice sometimes is not a good choice.

Regards,
Zoltßn

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=9336


C Ho
Intermediate Programmer/Analyst
B7322 SP 12.4
AS/400 coexistant with SQL Server 7.0
Sandbox: Xe AS/400 coexistant with CO on SQL 7.0
 

Zoltan_Gyimesi

Legendary Poster
Hi Catherine,
I do not think so. There is a (maybe?) simplier way.

1.) Create a new project for Version Copy, add yourself to the project with the appropriate User Role (having enough rights for all steps).
2.) Promote the status of your Project to the appropriate one.
3.) Drag'n Drop the versions that you want to copy from the User's default project to your new project (you have to have rights to do it in the user's default project!).
4.) Promote the status of your project to accomplish the Version Copy between Path Codes.

The mentioned statuses, user roles greatly could depend on your Object Management Configuration.

Zoltán
P.S.: The life is a bit harder using OMW but somtimes safer (?) and better controlled.

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 

CHo

VIP Member
Re: RE: Version Maintenance in Xe

Existing versions can be converted to Xe. You have to make sure that they come across to the TEMP environment that done as part of the preupgrade process. Make sure that you have the correct Client Access Express versions or else R9830512 won't bring over the specs to TEMP environment.

B7322 SP12.2 AS400 SQL 7.0
Sandbox: Xe SP 15 with central objects in SQL 7.0 on AS/400

Thanks for the info Zoltan!!!!

Another question on this topic for the wonderful list......

Can existing versions (in B7322) be converted to Xe or do they have to all
be recreated?

Our CNC hasn't found any documentation on this topic and enquiring minds
want to know....

Thanks,
Richard

B7322 SP12.2 AS400 SQL6.5 Moving to Xe




Richard,

Good issue.
Unfortunatley the situation is a bit complicated.
For all User Profile when you create them, automatically will be created a
DEFAULT project for that user (Not DEMO).
If a user creates a new version outside of OMW then it will be placed into
her/his DEFAULT project.

If you want to manipulate others' DEFAULt project then you have to be added
to these DEFAULT projects with an approriate User Role.

An other solution could be to configure your Object Management with limited
rights for the mentioned users and teach them to use OMW.

I know, the best choice sometimes is not a good choice.

Regards,
Zoltßn

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=9
336







C Ho
Intermediate Programmer/Analyst
B7322 SP 12.4
AS/400 coexistant with SQL Server 7.0
Sandbox: Xe AS/400 coexistant with CO on SQL 7.0
 
Richard,

We found that when we upgraded from B7332 to Xe, the versions still existed
(both batch and interactive), but no versions existed in Object Management
Workbench until a user checked out that object and checked it back in
(batch) or made a change to an interactive version. You will find, too,
that the definition of 'object' has changed in Xe to include items such as
UDC tables and menus. Once changed, these become part of your default
project. You will want to understand OMW well before upgrading - we learned
from experience about promoting versions in projects (batch versions, in
particular) after some headaches.

Tammy Baade
M&D Information Systems, Inc.
 
Top