| private_meta |
| (Getting the hang of it) |
| 2006-08-22 04:44 PM |
|
Microsoft Access Driver
|
Hi... I have a little question: i'm accessing a Access-Database via kix, but i'm not sure about the driver
$dsn = "DRIVER={Microsoft Access Driver (*.mdb)}; UID=; PWD=; DBQ=$DBpath"
i have this dsn, but i don't know if i have to install office to get the access driver on my system, or if this access driver works on all systems.
If it's not preinstalled, what driver/system file do i have to work with?
Does anyone here know more about it?
greets
Richard H.
|
| (KiX Supporter) |
| 2006-08-22 05:16 PM |
|
Re: Microsoft Access Driver
|
The easiest way is to look in your ODBC admin tool, there is a "drivers" tab that will show what's available.
| private_meta |
| (Getting the hang of it) |
| 2006-08-22 05:18 PM |
|
|
|
Re: Microsoft Access Driver
|
well... i don't have any workstation here that hasn't got office installed with access, that's why i don't have any idea if any of those drivers are preinstalled or are installed via office
|
NTDOC
|
| (KiX Master) |
| 2006-08-22 08:04 PM |
|
|
Re: Microsoft Access Driver
|
Well my 2000 and 2003 Servers without any Office both have Access driver. Not sure about workstations though, mine all have Office installed which might taint the results.
Though you could ENUM this Registry location to find out.
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI
|
Richard H.
|
| (KiX Supporter) |
| 2006-08-23 09:10 AM |
|
Re: Microsoft Access Driver
|
I can say that on a virgin workstation OS install with nothing else you probably won't get Access ODBC drivers. You may get text (csv) drivers but that's about it.
The problem is that the drivers themselves rarely do more than provide an interface to the DB backend, whether that is via local DLLs which have been installed with the DB or via network pipes. If you don't have Access components installed then the ODBC driver has nothing to talk to.
Do you specifically need Access? MDAC includes ODBC drivers for SQL server and Oracle, or you could use MSDE or mySQL.
If that doesn't help you then post a few details on what you are going to use it for, and maybe someone can suggest an alternative.
| Sealeopard |
| (KiX Master) |
| 2006-08-27 09:41 PM |
|
|
Re: Microsoft Access Driver
|
IIRC, MDAC also contaisn the MS Access drivers. A MS Office install si not requried to access an MS Access database via DSNs.
|
Richard H.
|
| (KiX Supporter) |
| 2006-08-29 09:17 AM |
|
Re: Microsoft Access Driver
|
Are you sure? When I checked on the latest download readme they weren't mentioned.
|
NTDOC
|
| (KiX Master) |
| 2006-08-29 08:56 PM |
|
|
|
Re: Microsoft Access Driver
|
An extraction of the files of MDAC 2.8 SP1 do not show any ACCESS files.
en_MDAC_TYP_2_8_sp1.exe
| Witto |
| (MM club member) |
| 2006-08-29 09:53 PM |
|
Re: Microsoft Access Driver
|
Is it the Jet Database Engine you require? How to obtain the latest service pack for the Microsoft Jet 4.0 Database Engine
| Witto |
| (MM club member) |
| 2006-08-30 12:04 AM |
|
|
|
Re: Microsoft Access Driver
|
On the page in the link above is written
Quote:
If you obtain the Jet 4.0 Service Pack 8 download for computers that are running Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows NT version 4.0, you will also receive the ODBC Desktop Driver Pack drivers. These drivers are included with the Windows 2000 operating system, the Windows XP operating system, and the Windows Server 2003 operating system.
So IMHO, it depends on the OS. If you were looking for ODBC for Apple, you could try and by Actual ODBC Driver for Access.
[Edit]
Oh yes, you were using KiX, so most probably, it will be on Windows.
private_meta last post was 22 august. Don't think he is listening anymore...
[/Edit]
| private_meta |
| (Getting the hang of it) |
| 2006-08-30 12:03 PM |
|
|
|
Re: Microsoft Access Driver
|
Oh, i am listening, but as a matter of fact my requirements for the script changed (sorry for not writing this here before) and it switched over to SQL Server :-x
| Witto |
| (MM club member) |
| 2006-08-30 01:04 PM |
|
|
|
Re: Microsoft Access Driver
|
Then you will need the Microsoft Data Access Components (MDAC) 2.8 SP1 I think.
This is if you are using one of these OS'es
Quote:
System Requirements
Supported Operating Systems: Windows 2000; Windows 98; Windows ME; Windows NT
Available for x86-based computers only
But most probably, you will have it...
I get the impression it is also more and more included in the OS, as on the MDAC download page is written:
Quote:
This redistributable installer for the MDAC 2.8 SP1 release installs the same Data Access components as Microsoft Windows XP SP2.
| private_meta |
| (Getting the hang of it) |
| 2006-08-30 02:06 PM |
|
|
|
Re: Microsoft Access Driver
|
According to my Information/Research the SQL Driver for SQL Server 2000 is already preinstalled on the systems (at least on WinXP/Win2k) so i won't have the need to install MDAC afterwards
| Witto |
| (MM club member) |
| 2006-08-30 03:17 PM |
|
|
|
Re: Microsoft Access Driver
|
True, for WXP, since SP2 (see quotes)
|
NTDOC
|
| (KiX Master) |
| 2006-08-30 10:06 PM |
|
|
|
Re: Microsoft Access Driver
|
Quote:
so i won't have the need to install MDAC afterwards
Not for pure functionality, but for security you should.
Out of the box Windows 2000 is at version 2.5 for MDAC
There are even hotfixes for MDAC that have come out aftre MDAC 2.8 SP1
So on a system that is getting automatic updates yeah they'll hot fix patch it, but it still won't auto apply 2.8 SP1
Which has better communication handling characteristics.
So when you get time you should think about updating your systems to MDAC 2.8 SP1 and then the hotfix.
| Witto |
| (MM club member) |
| 2006-08-30 10:36 PM |
|
|
|
Re: Microsoft Access Driver
|
Thx Doc for the confirmation. That is what I thought to have read. MDAC 2.8 SP1 supports Windows 2000.