Other dbxConnections.ini
Hi,
I have other file with information about connections and have an name
of AppDtb.Ini. It have all information about drives and connections.
When i choose the option Data in run-time it show the connections of
file dbxconnections.INI, but i need that show of other file. I change the
unit
daDBExpress.pas in method:
TDASqlSession.GetDatabaseNames(aList: TStrings) and recompile my
application,
but don't work fine. After this i try compile the packge RBDbe76.dpk and
don't
work fine. It continue show the connection from dbxConnections.INI...
What's wrong?
I have other file with information about connections and have an name
of AppDtb.Ini. It have all information about drives and connections.
When i choose the option Data in run-time it show the connections of
file dbxconnections.INI, but i need that show of other file. I change the
unit
daDBExpress.pas in method:
TDASqlSession.GetDatabaseNames(aList: TStrings) and recompile my
application,
but don't work fine. After this i try compile the packge RBDbe76.dpk and
don't
work fine. It continue show the connection from dbxConnections.INI...
What's wrong?
This discussion has been closed.
Comments
Be sure you are using the updated daDBExpress.pas file when you compile your
application. Check that your library path is pointing towards
\RBuilder\Source\... and that you remove the path point towards
\RBuilder\Lib\...
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I do this, first check that my library was pointing to
\RBuilder\Source\... and after removed the path point towards
\RBuilder\Lib\..., but continue show just connections from
dbxconnetions.Ini. What's the place that it call this Method
GetDatabaseNames? What I'm do wrong? What i can do to solve this
problem???
thanks
Here are the lines of code that access the dbxConnections.ini file in
ReportBuilder...
if (aList.Count = 0) then
GetConnectionAdmin.GetConnectionNames(aList, '');
Be sure you are commenting or deleting these lines if you do not want to use
the default .ini file. Next you will need to add your own code in it's
place to access the custom .ini file you created. Set a break point in your
code to be sure everything is running correctly and trace through it to be
sure the correct .ini file is being accessed.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com