Hi
Mark,
The
DatabaseName property is kinda like an alias for your app, not the actual
gdb name so it usually has my Application name as it's
value.
If you
double click on the TDatabase component in the designer you get a popup
window where you can set parameters. I set Server Name etc in
here
an
example of one of mine (Parameter Overrides that is) is...
SERVER
NAME=C:\ibdata\equis\data\equis.gdb
;SERVER NAME= USER NAME=SYSDBA ;PASSWORD=
PASSWORD=MASTERKEY OPEN MODE=READ/WRITE SCHEMA CACHE SIZE=8 LANGDRIVER= SQLQRYMODE= SQLPASSTHRU MODE=SHARED AUTOCOMMIT SCHEMA CACHE TIME=-1 MAX ROWS=-1 BATCH COUNT=200 ENABLE SCHEMA CACHE=FALSE SCHEMA CACHE DIR= ENABLE BCD=TRUE BLOBS TO CACHE=64 BLOB SIZE=32 I
leave a commented out "blank Server Name" and "Password" (this is the
Interbase password option) there for creating deployable builds (these values
are assigned at run-time and typically held in an ini file (pasword is of course
stored encrypted in the ini file). I probably should achieve this via
compiler directives or something but for now it works - I just have to remeber
to use the blanked options for the actual build.
When
you use say a TQuery component on a form that has access to the form with the
TDatabase component you will see your DatabaseName appear as one of the options
in the TQuery's database property in the object inspector.
Hope
yopu can follow this - if you need more examples or info then email me
directly
regards
|
- [DUG]: Connecting to Interbase Mark Howard
- RE: [DUG]: Connecting to Interbase David Smith
- Re: [DUG]: Connecting to Interbase Mark Howard
- RE: [DUG]: Connecting to Interbase James Low
- Re: [DUG]: Connecting to Interbase Mark Howard
- RE: [DUG]: Connecting to Interbase Willie
- RE: [DUG]: Connecting to Interbase James Low
- Re: [DUG]: Connecting to Interbase Mark Howard
- Re: [DUG]: Connecting to Interbase Mark Howard
- RE: [DUG]: Connecting to Interbase James Low
- Re: [DUG]: Connecting to Interbase Willie
- Re: [DUG]: Connecting to Interbase Mark Howard