Omwb - still problems

Question

Dear all - any ideas on this?
I am running the latest release of omwb2003.mde on XP.
I first get the Error #3029 - DAO.DbEngine - Not valid account name or password but only for the schema export, the tables export fine (I guess since the XMLExporter is not involved there).
By playing a bit m ore and losing substantial time, I found that if I Cancel the export just before I type into the Logon box I get the well-known message: XMLExporter - Method 'DBEngine' of object '_Application' failed message.
1) There is nothing wrong with the passwords since I log onto the db all the time.
2) Tried to re-register the Dao360.dll, re-arrange the References and all the other stuff from previous posts - to no avail.
A) The db is spit into front and back end, joined to a workgroup.
B) VB code compiles fine.
Note the the authors of the exporter - how much easier it would be if you just made the code public - could have fixed it myself. It's to migrate to Oracle so why not to open-source it instead of making big secrets out it! This just makes people give up on your product in no time! They need to go through the java MWBench anyways!
Icecube

Answer 1

What I am saying is that the access_exporter is brain-dead and so it is (spent 5 hours to make it work - will never get this time back). I guess the WB itself probably works but how to use it if I don't have the files from the exporter?
The Oracle ODBC driver works fine (was installed at the same time as XE) - the problem is in the XP registry where MS puts, per default, references to the old Oracle 8 DLLs. The description of the problem is to be found in my other post.
I used one of the commercial packages available on the internet for USD 50. I would not like to mention it as not to seem to promote them. However, the software is as sweet as it comes - opens - logs into Access and the Oracle instance and transfer everything including P,R constraints, load data etc. All about in 5 minutes. Sweet, in my book just much easier then mucking around with the access-exporter which is written in Access which makes it unsuitable for serious code to start with and then the Java WB (which seems to be ok, but who cares for nice pictures - make it fast and painless and people will use it ;-)
Icecube