>> When linking I get these error messages:
>> #myprg.obj(myprg)
>> # Error 42: Symbol Undefined __Class_3dbi4odbc12OdbcDatabase12OdbcDatabase
>> #myprg.obj(myprg)
>> # Error 42: Symbol Undefined
>> _D3dbi4odbc12OdbcDatabase12OdbcDatabase5_ctorFZC3dbi
>> #4odbc12OdbcDatabase12OdbcDatabase
>> #--- errorlevel 2
>> If I don't want to create a new instance (OdbcDatabase x;) it's fine but
>> cannot be used.
>>
>> What have I done wrong?
>
>This usually happend when you've not added the source files to the command line.

Ok, I've ran into this problem before. But there's a *lot* of modules for this single one. How can I avoid the command line thing?

"Nahon" <lburger@hu.tesco-europe.com> wrote in message news:ei4qn3$s4q$1@digitaldaemon.com...
>>> When linking I get these error messages:
>>> #myprg.obj(myprg)
>>> # Error 42: Symbol Undefined
>>> __Class_3dbi4odbc12OdbcDatabase12OdbcDatabase
>>> #myprg.obj(myprg)
>>> # Error 42: Symbol Undefined
>>> _D3dbi4odbc12OdbcDatabase12OdbcDatabase5_ctorFZC3dbi
>>> #4odbc12OdbcDatabase12OdbcDatabase
>>> #--- errorlevel 2
>>> If I don't want to create a new instance (OdbcDatabase x;) it's fine but
>>> cannot be used.
>>>
>>> What have I done wrong?
>>
>>This usually happend when you've not added the source files to the command line.
>
> Ok, I've ran into this problem before. But there's a *lot* of modules for
> this
> single one. How can I avoid the command line thing?

I wouldn't call it a "problem" as such: you have to tell the compiler which files to compile. However, Derek Parnell's Bud (nee Build) tool can make the task of compiling a lot less tedious. http://www.dsource.org/projects/build/wiki