Subject | Re: [IBO] Re: ibo3.6 to ibo4.3 conversion problem.. |
---|---|
Author | Helen Borrie |
Post date | 2003-12-12T00:07:35Z |
Craig,
At 08:46 PM 11/12/2003 +0000, you wrote:
You still have some library referenced in a uses clause somewhere, that
uses the bde. Some things to look for:
1) A uses clause including the library dbtables. This reference must be
commented out.
2) Use of the AliasName property in components. I recommend *removing*
this. It has caused problems before and you really don't need it.
3) Use of the DatabaseName property to store the server and path
string. Instead, change this to something like "MyDB" and use the
properties Server, Path and Protocol.
4) Due to one or more of the above, a data access component that is trying
to create its own connection. After setting the DatabaseName to something
that is not the server/path string, go through each data access component,
click the Databasename dropdown and select whatever is displayed there -
either the "friendly" name that you placed in the IBODatabase Databasename,
or the object name of the IBODatabase.
NB - if you see a BDE alias anywhere, then something is wrong with your
TIBODatabase setup. If you don't find the problem, open "as text" the DFM
file that contains your TIBODatabase properties, copy it, and paste to the
list.
Helen
At 08:46 PM 11/12/2003 +0000, you wrote:
>Jason,Craig,
>
>Thanks for the reply, I performed the following:
>
>I reinstalled BCB6 and created a small app using BDE components and
>it compiles.
>
>Reinstalled IBOv4.3 and created a small app using IBO components and
>the BDE DataSource object, it compiles.
>
>Tried recompiling my app and still have the same problem. This app
>started out as a BDE project and converted to IBO under BCB3. The
>only the BDE DataSource is used, the rest is IBO components.
>
>Still confused.....
You still have some library referenced in a uses clause somewhere, that
uses the bde. Some things to look for:
1) A uses clause including the library dbtables. This reference must be
commented out.
2) Use of the AliasName property in components. I recommend *removing*
this. It has caused problems before and you really don't need it.
3) Use of the DatabaseName property to store the server and path
string. Instead, change this to something like "MyDB" and use the
properties Server, Path and Protocol.
4) Due to one or more of the above, a data access component that is trying
to create its own connection. After setting the DatabaseName to something
that is not the server/path string, go through each data access component,
click the Databasename dropdown and select whatever is displayed there -
either the "friendly" name that you placed in the IBODatabase Databasename,
or the object name of the IBODatabase.
NB - if you see a BDE alias anywhere, then something is wrong with your
TIBODatabase setup. If you don't find the problem, open "as text" the DFM
file that contains your TIBODatabase properties, copy it, and paste to the
list.
Helen