> I have realised what the problem is. The scripts default to the 'weberp'
> database and I am using it against another one.
> The question is, will this corrupt the old one?
I, too, repeat that far too often. I, personally, would recommend that
lines, 12,19d be deleted and if a db creation script is needed that it
be an additional script. With the new companies option, I think it
would be much more clear.
I was bitten by it again this morning creating a new 303 installation
and no it shouldn't overwrite or corrupt your weberp database. It
should just error out when trying to create.
> Its good to see even the experienced also make the errors us novices make!!!
We are all novices, IMO. I am having my problems learning webERP and
its development culture that I feel that I need to understand to
eventually be in a position to help the project in some way.
> For general use, I suppose the script is OK, but for people working with a
> couple databases and wanting to test new releases etc, your suggestion is a
> good idea.
> Going forward, the best solution could be a setup or install pack that you
> run after installation, like egroupware or others, where you enter setup
> details online!
Being an old fart that has used only unix since the early 1980's, I'm
not a big fan of webbased or automated application installs but they do
usually work and are probably the better option for average
installation requirements. It is something that should definitely be
looked at as the dust settles a bit.