-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Frank,
| I suppose you deployed it as UNO package? yes, I used dmake to build a package. I added it to OOo-Base with unopkg ~ and it's registered there without problems. | - Ensure that the DataAccess.xcu is part of the package, and has proper | content (for the definition of "proper", you can probably spy at | existing driver packages which work :), e.g. the PostgreSQL driver) I have a DataAccess.xcu. I used the .xcu from old sqlite driver and changed a little bit. And I tried it from postgresql-sdbc. It doesn't work. | - Ensure that the driver library is compatible with the version into | which you deployed it. I am not sure whether the package manager would | detect a fault here. On windows, try "depends <your_library_name>", on | Linux, IIRC, "ldd <your_library_name>" (you probbaly know this better | than me :) He doesn't found some libs - but that happend with old sqlite3-driver, too. That driver appear in the list and work without problems. I added the path to connectivity/unxlgni6.pro/lib to my ld-path and now he found alle libs. But still... driver doesn't appear in the list. | - If this doesn't work ... hmm. Debug into | dbaccess/source/ui/misc/dsntypes.cxx, in particular | initUserDriverTypes, and see whether your driver is listed there. If | not, your DataAccess.xcu is wrong. If yes, debug the callers to see | why your type is ignored later. I looked into the sources. But how can I debug into it? I only have my CVS-workspace with a compiled build and I use 'dmake' with my tcsh to build a package. ;-) Regards, André -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEoWfpbwhJf8Ldh+IRAjH/AJ0cYbMQmY2iPgG82Zi+DKuTsWfQyQCffTob D1nXizT0MPdsNvMmJLHApbs= =LVKU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
