Register odbc dll windows

If he has expertise let him show it off, I think the first poster sounds really stupid for being so bent out of shape with something that is frankly free installs with Dynamics Management Reporter software to Migrate Company reporting building blocks from fRx 6.

Kudos to the experts, great post Albert and keep showing off that brain. Your diatribe was very entertaining, but unfortunately you completely missed the point. Unless you also feel that pounding on people's head in support forums is actually the way things should be done?

The reason why one would want to maintain both the 32 bits and 64 bits versions of a driver is totally irrelevant to the whole discussion. Companies have legacy software that they must keep running, and in some cases they don't have the resources, or maybe even knowledge, to keep them running.

The fact that the drivers ARE installed when using an ISO of Office , but not when using the web installer shows that at some level, Microsoft also feels it's necessary to provide them for backward compatibility. The real question is "why are these drivers not installed with the web installer , but they are with the ISO?

Furthermore, why would it be clear to someone that installing a driver for Office is actually proper for Office ? The way you and Mr. Kallal present your facts is condescending at best. Like saying "The above knowledge is a result of having 'basic' familiar with the ACE database engine", and "Found the above in about 5 seconds of my time with Bing search" implies that the OP is an idiot for not having this basic knowledge, but also an idiot for not understanding that a solution for Office will also apply to Office I really fail to understand why people like you bother participating on support forums if all you can find to reply are insults.

After all, nobody's forcing you to help others. If you think a question is not worth your time and effort, then simply ignore it. In my case, I was confronted to the exact same issue, and it also took me some time to figure out why I was having the issue after installing Office from the web installer, but not on other workstations where the ISO was used.

I might not be the brightest bulb on the shelf, but I'm certainly not the dumbest either, and it did cost me a few hours of research, at my own expense, to solve it.

So, if all you can think of in your next reply is to insult me or the OP, save yourself the effort, and don't bother replying. So, answer me this, anyone who can: How does one respond to these seemingly simple directives in this environment? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. I should mention of course I already tried regsvr DLL set up and working everywhere, made corresponding registry entries on the bit machine.

Copy the library files to a suitable directory. Optionally, copy the help files. For these files to be accessible through the help system, they must be installed in the Windows system directory:.

If you installed these files into a non-default location, change the references to the DLL files and command location in the above statement. ADO: rs. DAO: rs. RDO: rs. NET and C C sharp. In this post, we will show you 5 solutions that are proved to be effective. In this post, we will show you how to reg DLL files via regsvr There are two methods. You can select your preferred one to do the job.

The following is an example:. Type cmd and select Run as administrator from the pop-up Command Prompt options. Then, you need to type the regsvr32 command.