Checking Versions out on Terminal Server

Under ERP8 we have discovered that once we check a version in, while we are
logged in to a terminal server; we cannot check it back out. But if we go to
a Fat Client it works fine. Is this normal under ERP8?

-Brian

ERP8 sp21_I1 (with update 1)
Windows 2k
SQL Server 2k
Terminal Server 2K
Citrix 1.8



William “Brian” Wilkinson
Quickie Manufacturing
[email protected]
856-829-7900 x143

This is normal for a Terminal Server. You can create a version on a Terminal Server - and check it in, (which would "JITI" it to other Terminal Servers) - but you cannot then make a change to the version on a Terminal Server - you must go to a fat client to do this - and really if you make a change, you need to redeploy that change if its for a UBE.

I miss 7332 already

-Brian



William “Brian” Wilkinson
Quickie Manufacturing
[email protected]
856-829-7900 x143

Re: RE: Checking Versions out on Terminal Server

I agree with you. I hate that you cannot checkout a version on terminal server. Here is a little trick though. If you put OWDEVELOPER=TRUE in the [DEBUG] section of your ini - you will be able to check versions in and out. It also allows development through OMW on a TS.

Thanks!
M

RE: RE: Checking Versions out on Terminal Server

Thanks, that will be a huge help during our conversion phase.

-Brian



William “Brian” Wilkinson
Quickie Manufacturing
[email protected]
856-829-7900 x143

Re: RE: Checking Versions out on Terminal Server

Melissa, et al...

Yes, the OWDEVELOPER=TRUE will allow development tool access on a
terminal server, but beware...remember, unless you've set up the terminal
server for development use (doubtful in a production environment),
everyone who modifies, gets, check's out, is changing the same set of
spec files on the terminal server, THE SAME SPEC FILES USED BY ALL OTHER
USERS...and if you've got two or more people trying to modify the same
file at the same time....Well then, why YES, YOU TOO can have the fun of
spec file corruption, and all the wonderful quirky problems, downtime,
unnecessary troubleshooting, package (re)deployments, and the such that
spec file corruption brings to the table.

There are valid reasons that check-outs are not available on a terminal
server by default...in a properly configured system...if a user needs a
different version, he/she can copy one that exists, change PO's and/or
Data Selection, run it, and then request that a version that matches the
new one be created via the normal development cycle if it needs to be
shared by others. This can all be done without turning on the
OWDEVELOPER=TRUE floodgate. That way, production user can create a
version if they need to, and if that version is deemed important enough
to be shared by more than just the creating user, it can be created and
promoted via the proper change management cycle.

Of course, that's just my opinion...I could be wrong...

Dennis Miller...er....Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!

RE: RE: Checking Versions out on Terminal Server

When you say development, does this include full development, such as new UBE's, tables, etc?

Re: RE: Checking Versions out on Terminal Server

Yes, when set up properly, a terminal server can be used for FULL
development...though the number of developers per terminal server is
about half the number of regular users.

Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!

Re: RE: Checking Versions out on Terminal Server

I guess I should have added that in my response - we only let admins have OWDEVELOPER=TRUE.

Thanks,
Melissa