[U2] The Pick

2011-06-16 Thread Boydell, Stuart
This caught my eye - Anyone see any typographical similarities? http://www.the-pick.com.au/ Cheers, Stuart Boydell ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users

Re: [U2] Conversion Documentation

2011-06-16 Thread Symeon Breen
Lol - how many times have i done x = var1 var2 instead of x = var1 : var2 -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Tony Gravagno Sent: 16 June 2011 01:35 To: u2-users@listserver.u2ug.org Subject: Re: [U2]

[U2] Uniobjects UOEncoding

2011-06-16 Thread Symeon Breen
Hi I have some utf8 encoded data in my unidata databse, and i want to display it on a web page using uniobjects.net. The data is coming through as iso-8859-1 encoded, so i use the UOEncoding as UniSession udSesh =UniObjects(xxx, yyy, zzz,aaa, udcs); Encoding en=Encoding.UTF8;

[U2] Question about updating customer's systems...

2011-06-16 Thread Tom Whitmore
Hi, We develop software for college bookstores. Over the past year and a half, we implemented PRC's version control software in-house, which has helped us improve the development and release process. We are no looking at how to improve the installation process at our customers. At this

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Doug Averch
Hi Tom: We had a similar problem years ago trying to deliver our customers consistent releases that we could script. We tried Windows bat files and Unix shell scripts but each release was never quite right. Our staff would forget this file or this dictionary or just plain copy the wrong account

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Tom Whitmore
Thanks Doug, PRC does a great job of tracking what needs to go where, as we pack up the update. The problems we are currently having are 1) our customers want updates after their business hours (read late into the night) 2) our customers have custom code 3) our customers would like to be able

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Kevin King
We typically recommend that customers have at minimum two accounts, a test account and a live account which are virtually identical and share nothing. This allows us to install to the test account and have them test the code and then we take the same ravel files and roll it up to their production

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Doug Averch
Hi Tom; 1) This is not a problem if you allow customers to do their on updates by allowing access to the base system or sending them it to them on a thumb drive, or allowing them to upload the base system via FTP, or some other mechanism. 2) This is always a problem that requires structure from

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Dan McGrath
I would also suggest either of the following: 1) If possible, run Dev/Test/Prod on separate machines. Obviously, this requests budget, but if your production system is the lifeblood of your company, it is worth it. Otherwise: 2) Have the accounts set up with appropriate file permissions

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Wols Lists
On 16/06/11 17:18, Doug Averch wrote: On some of our Client systems we open 3 connections and use all of those connections to updating their site simultaneously. We do not have to do linear installs anymore which cuts our installation time from several hours per site to about 15 minutes

Re: [U2] RPC timeouts

2011-06-16 Thread John Hester
The timeout value is in seconds so the default is 1 hour. The optimal setting is going to be unique to your environment and depends on how you're using unirpc. The default is fine for us because we mainly have connections from an app server that last a few seconds at most. I actually have

Re: [U2] Question about updating customer's systems...

2011-06-16 Thread Kate Stanton
Use colours, so users know if they are in Live or Test (eg normal grey for live, yellow background for test). The users can happily copy live data to test, do any conversions, run things to make sure all OK. Before we did this, users would do some testing, then forget they were not in Live, and