Setup types not case sensitive, causes dupe error

[NewsArchive]

[Monday, April 25, 2005 9:09 PM]

I put a setup type of "Install with empty databases", then decided that I
wanted to capitalize the word "empty", thus making the setup type into
"Install with EMPTY databases".

I cant do that, it says that this setup type already exists.

I had to change the name to ...empty2... then to ...EMPTY.... to get it to
work.

--

Mark

[NewsArchive]

[Tuesday, April 26, 2005 2:20 PM]

By the way, the "Setup Type Name" is never displayed to the end user. It's
used in your script (e.g. "Set Active Setup Type" script function).

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[NewsArchive]

[Tuesday, April 26, 2005 4:06 PM]

> By the way, the "Setup Type Name" is never displayed to the end user. It's
> used in your script (e.g. "Set Active Setup Type" script function).

I see that now. I didnt yesterday, other than thinking it was a bug because
the names never appeared in the installer when testing.

The changing of the case shouldnt cause this behavior, regardless of the
desired use of the field, imo.
--

Mark

[NewsArchive]

[Tuesday, April 26, 2005 4:16 PM]

Yes, I agree!

Friedrich