Subject | Re: [firebird-support] How to make my own installer install firebird with my application in vb.net |
---|---|
Author | Scott Morgan |
Post date | 2014-05-01T10:46:33Z |
On Wednesday, April 30, 2014 1:49 PM, "sukhendass@..."
installer (or creating a small util to make the required changes via
FB's services API). There's a lot of problems copying .fdb files between
systems, and also problems writing into "Program Files" directories that
modern Windows systems hide from you (if you're not careful, it can look
like you copied/edited a file there but in reality it's located
somewhere else).
More generally:
Could your app work with fbembed.dll? Would save you a lot of work
trying to install the full server.
Or, Firebird v3 will be out soon (maybe), which allows passwords to be
stored with the database file rather than with security2.fdb. A major
help for situations like this.
Scott
>Rather than copying security2.fdb, I'd recommend using GSEC in your
> I want to create my own installation to install firebird with my
> application.
> i have downloaded the manual script and i need to attach my own
> security2.fdb as my own userid/password is saved with this db.I have
> replaced my system security2.fdb in the firebird folder where the
> downloaded security2.fdb is located but when i run install_classic.bat
> it runs successfuly but when i connect from flamerobin with my shipped
> db it gives an error msg and i have checked firebird service is running.
> alt
installer (or creating a small util to make the required changes via
FB's services API). There's a lot of problems copying .fdb files between
systems, and also problems writing into "Program Files" directories that
modern Windows systems hide from you (if you're not careful, it can look
like you copied/edited a file there but in reality it's located
somewhere else).
More generally:
Could your app work with fbembed.dll? Would save you a lot of work
trying to install the full server.
Or, Firebird v3 will be out soon (maybe), which allows passwords to be
stored with the database file rather than with security2.fdb. A major
help for situations like this.
Scott