Conference iosg::all-in-1_v30

    I don't think it would be a supported configuration, but I suppose that
    the way that you do business and support the product in your country is
    your problem!!!
    
    You're right that Finnish isn't supported as a second language by the
    US country kit, but I don't know how the Finland country kit is set up.
    It wouldn't be very hard (technically) to make the Finland country kit
    allow Finnish as a second language, or you could just change things
    after the English installation. You'd need a BLISS compiler to change
    OAMARKET, and to edit A1.CLD, but it's not very difficult.
    
    Then you could use the 'ALLIN1' licence for all the English users, and
    a Finnish UI capacity licence for the second language. If that was too
    expensive, you could use a personal UI licence, although they aren't
    really supported. You should check the prices to see what looks best.
    
    I think that would be the best way to get the system setup to suit your
    mostly English users.
    
    But I think that your plan would probably work too. It just seems more
    sensible to have English as the primary language if that's what most
    people use.
    
    Graham

    Asko,
    
    I'm disappointed! What have you been in Frankfurt for. :-)
    
    I'm not sure about the licensing combination, but you can definitely
    combine Finnish with English, and it doesn't matter which language you
    install first. Also, the Finnsih C component supports English, Finnish
    and Swedish as languages. Even if a LATIN-1 language is not directly
    supported you can combine the installation with any other LATIN-1
    language using a few small tricks.
    
     	regards,
    	Stefan

    Hi Paul,
    
    must have missed your reply by seconds.
    
    I understand your explanation, but don't we have a problem still with
    installing personal licenses for secondary languages? As far as I know
    the customer can't run bilingual or multilingual systems with only 
    personal licenses installed.
    
    	correct me if I'm wrong...
    	Stefan

    
    	RE: .0
    
    	This is EXACTLY what the marketing folks were scared to death of
    	during the V3.0 licensing review. Technically what you suggest
    	does work, but there was a STRONG push from marketing to get the
    	code to actually detect this configuration and disallow it. The
    	problem? $$$$$'s. The primary personal licenses are very cheap
    	as they only license one user, the secondary capacity licenses
    	are also very cheap because it is expected that the customer has
    	paid a lot for his primary CAPACITY license which covers the base
    	engineering cost of ALL-IN-1, and the secondary licenses should
    	only cover translation costs.
    
    	So you are giving the product away! For this reason, the business
    	people have outlawed this configuration of licenses.
    
    	Please don't sell capacity secondary licenses if you don't have
    	capacity primary licenses.
    
    Regards,
    Paul

    Hello,
    
re.3    > I'm disappointed! What have you been in Frankfurt for. :-)
    
    Perhaps Asko read note 954...
    
    Regards,
    
    Jan
    

    
    	In V3.0 you can technically have personal licenses for secondary
    	languages. (So called PUI licenses). These are new to V3.0. As
    	far as I know, the business people have decided that we won't sell
    	any, but I guess each country could possibly differ.
    
    Regards,
    Paul

    
    	RE: .6
    
    	954 was an internal VTX problem. :-)
    
    Regards,
    Paul

	Thanks for the replies.

	Paul, the money is not the matter (this time), because the customer
	has already paid one 'full' payment for one language and is willing
	to pay needed personal licenses for the secondary language. They just
	want to use less the primary language and more secondary language.
	We also found out the price for the personal license.

	Stefan (hi again), because I like to keep this as clear as possible,
	I like to use Finnish kits, and that's why to install Finnish as a
	primary language and English as a secondary language. This is supported
	way to do it with Finnish country kit as far as I know.
	But because most, almost all users use English, they have full cost
	capacity license, and they want to buy personal license(s) for Finnish
	language, the primary language, if possible.

	May be that I was working in Frankfurt too hard to learn anything.
	At least I didn't had time to drink enough Hefewaisse 8-)

	Graham, it's a good idea to modify OAMARKET, but then I have to do it
	every time the customer is upgrading ALL-IN-1? And after I have retired
	(please read my personal name), who will remember to do it 8-)

	So, bottom line, it seems to me like it will work technically, and
	if our license peoples agree, I'll try it (unless you give me new
	suggestions or cautions).

		Asko

    "Only 7018 days to retirement"?
    
    D.

	Oooohhhhh, there are Finnish speaking ALL-IN-1 gurus.

	May be that I should speak about Finnish country kit with you 8-)

		Asko

    Coincidentally, you and I retire in the same year. Hence I can offer
    you this advice, knowing that we will *both* not have a problem when it
    breaks!!!! For exact date, see the expiry date of files in the V2.2
    kit....
    
    I still think that you should install English as the first language,
    and from what Stefan says, the Finnish country kit should let you do
    that and add Finnish as a second language, without any changes to the
    kit.
    
    Graham