64 Bit Toad and 32 Bit Access

Toad for Oracle
23

Hi, John.

Thank you so much for your help. As you pointed out, I had the folder C:\Program Files (x86)\Common Files\microsoft shared\DAO, but I did not have the DAO folder in C:\Program Files\Common Files\Microsoft Shared. dao360.dll is the only file in the C:\Program Files (x86)\Common Files\microsoft shared\DAO folder.

I copied C:\Program Files (x86)\Common Files\microsoft shared\DAO to C:\Program Files\Common Files\Microsoft Shared\ (still only the one file). So now it looks like below. I tested it, and unfortunately, the error persisted. I also reregistered the dll in the new location (non-x86) location, and still get the error. This is really bugging me.

I appreciate all your help.

5-3-2017 12-06-48 PM.png
5-3-2017 12-06-48 PM.png718×315 17.8 KB

24

Ugh, I thought that was going to solve it! Yes, just one file in that folder. And mine has the name, size, and timestamp. hmmm…

For what it’s worth, I never registered it in either location.

25

I still get the error if I try to export to a .mdb file, but .accdb works.

26

Ta-daaa!

Silly me. I just assumed that TOAD would export to .mdb since that’s the file format it offers. I changed it to .accdb, like you suggested, and it exported like a champ! I’ve never felt so foolish and so relieved at the same time.

Thank you so much for your help, John.

27

Don’t feel bad - it SHOULD export to mdb also! That seems like a bug and although it’s way too late to do anything about it for 11.6, I’ll make sure it’s right in the current version.

28

Hi John,

I also have a frequent (once per week) need to export data from Oracle to two different Access databases, in order to provide the data to other people. I'm using TOAD version 12.10.0.30 (64-bit). I'm also using Office 2013 Professional, 32-bit (Microsoft recommends 32-bit Office for most users). If I read this thread correct, it sounds like one should be able to export to 32-bit Access using 64-bit TOAD? I have not been able to do so, including after copying the DAO file you indicated above. It would really be nice, especially since TOAD can export to 32-bit Excel.

I did not want to "downgrade" my installation of TOAD to 32-bit just to satisfy this weekly requirement, so I created a virtual machine with the same version of TOAD, but with Office 2013, 64-bit. That allows me to export to Access just fine, but I simply have not found a way to export from 64-bit TOAD to 32-bit Access.

If your team is going to look into this for version next, please improve a few issues that are a bit of a pain.

1.) I have two "template" Access database files, which have empty tables with the correct table names, column names and data types. I had to do this because in some cases TOAD was converting numbers to text data type. These templates also include some saved queries for the user. The names are "Drawing_PMP_Report.accdb" and "IRCS_Records.accdb":

1_TempateFiles.jpeg

If I use the Export Dataset feature, and I need to export to the other database (Drawing_PMP_Report.accdb, in this example), I cannot use the Build Button (blue arrow) to select the database:

2_ExportDataset_SelectFile.jpeg
2_ExportDataset_SelectFile.jpeg487×502 71.2 KB

If I do, I get a prompt that demands that I replace the database!

4_ReplacePrompt.jpeg

No, I do not want to replace it, because it is a saved template. I simply want to select it as the target for an export.

Instead, I have to manually edit the name of the database, by typing it in, as indicated below:

6_ReadyToExport.jpeg

Notice also, in the above image, that the table name is detected (correctly) and I have the option selected to Append rows (if columns match). However, I always get the following confirmation prompt. I have to be careful to click on Append Tables, instead of accidentally hitting Overwrite Tables. Why is the above option not honored?

7_ConfirmationPrompt.jpeg

Thank You.

29

Hi Tom,

I didn’t mean to imply that you could export to 32 bit access from 64 bit Toad. The reason that exporting to Excel is more flexible is that Toad is creating the Excel file from scratch. In fact, you don’t even need to have Excel (or any kind of excel engine) installed to export to Excel.

The reason for the prompt (in your last question, not when clicking the … button) is that you have “If file exists” set to “prompt for append/overwrite/insert”. (Sounds like you’d prefer to have that one set to “create tables in MDB file”) The “Append rows” option that you have selected below refers what to do if the table exists within the file, not what to do if the file exists.

Regarding the prompt when you click the ‘…’ button at the top, well, that’s just a “file already exists” warning from the Save File dialog. You could actually tell it Yes if you wanted instead of manually editing. It doesn’t know that the export action will later be smart enough to append if you so choose (but maybe it should know that, to avoid confusion!)

-John

30

Rex, the .mdb bug was fixed in Toad 12.5.

31

Hi John,

I didn't mean to imply that you could export to 32 bit access from 64 bit Toad.

Okay, my misunderstanding of the thread.

(Sounds like you'd prefer to have that one set to "create tables in MDB file")

I’m using the .accdb file format, not the .mdb file format.

In addition, I do not want TOAD to create the tables; I only want TOAD to append to existing tables in each template file.

Regarding the prompt when you click the '...' button at the top, well, that's just a "file already exists" warning from the Save File dialog.

It seems to be an overwrite warning. I absolutely do not want TOAD to replace the file—just append to it.

I think this process could be engineered to be a bit more fluid for the user.

Tom

32

I’m using the .accdb file format, not the .mdb file format.

I know. It works for either. I'll change the text so it is not specific to one file extension or another. I see how that can be misleading.

It seems to be an overwrite warning. I absolutely do not want TOAD to replace the file—just append to it.

Yes it does look that way. Test it.

I think this process could be engineered to be a bit more fluid for the user.

agreed.

33

Hey guys,

Sorry to revive this old post, does this limitation of needing to have the same bit-ness for exporting to Access still exist in the newer version of Toad for Oracle 16 and Access 365?

Any chance to circumvent it to be transferring data between environments (no data pump also)? I work on a server and my IT guys simply don't want to install it ...

Thanks

34

Nothing has changed here. The bitness of Toad needs to match the bitness of the MS Access engine (which can differ from the bitness of MS Access itself).

Here are some links to install it, if you need them.

2010: https://www.microsoft.com/en-us/download/details.aspx?id=13255
2013: https://www.microsoft.com/en-us/download/details.aspx?id=39358
2016: https://www.microsoft.com/en-us/download/details.aspx?id=50040
Office 365: Download and install Microsoft 365 Access Runtime - Microsoft Support