Access 2007 / ODBC linked tables to SQL SERVER / Vista 64 bit erro

[Safety Man]

I am having various problems getting my ACCESS 2003 database running on a 64
bit vista SP1(native) installation. This database uses linked tables to a
SQL Server
database hosted on a 64 bit windows 2003 R2 / SQL 2005 64 bit.

Yes, the same MDB/MDE file works on the following systems
Windows XP (32 bit)
WINDOWS XP SP1 (32 bit)
WINDOWS XP SP2 (32 bit)
Windows VISTA (32 bit)
Windows VISTA (32 bit) w/ SP1 installed
Windows VISTA SP1(native) 32 bit

Yes it works on the office versions on the above Operating Systems.
OFFICE XP SP1-SP4
OFFICE 2003 sp1-sp3
OFFICE 2007 SP1

Something is a matter with the ACCESS 2007 application using the ODBC
(linked Table) connections on the ACCESS MDB /MDE file while running on a 64
bit vista platform. (note: it is compiled to work in ACCESS 2003)

What is strange: I can create the system DSN and test the connectivity and
it all works great; until I try running the application.

ERRORS I RECIEVE:
1> Error: ODBC Error: Unknown ODBC Database source ...
2> ODBC - connection to 'DNSNAME' failed

When going to the dataview/table view of the database(not the database
forms). I tried to click on one of the sql linked tables and get the error
"Can't open the table on DataSheet View"

Other strange errors(probably vista related).
1>A potential security concern has been identified - this file might contain
unsafe content that could harm your computer. Warning it is not possible to
determine that this content cam from a trustworthy source.
2>You are logged on with non-administrative privledges. System DSNs could
not be created or modified.


Other strange thing: I created a native ACCESS 2007 application and tried to
created a linked table to the same SQL Database and the system DSNs would not
show up. Only machine DSNs (which I think are system DSNs) and USER DSNs.
But it gave me a security warning anyhow when I tried to create a system dsn
and set I could not do it.

What is up with this???

Thanks,

Doug Lubey of Louisiana
www.douglubey.com

SEARCH ENGINE REFERENCE:
VISTA Microsoft Access Error Unknown ODBC DataSource
http://www.vistaheads.com/forums/mi...dbc-missing-access-64-bit-vista-ultimate.html
Microsoft Data Access Components Vista 64 bit
Microsoft Access 2007 "Error Unknown ODBC DataSource" VISTA
VISTA Error: ODBC Error: Unknown ODBC Database source
VISTA ODBC You are logged on with non-administrative privledges. System
DSNs could not be created or modified
VISTA ODBC You are logged on with non-administrative privileges. System DSNs
could not be created or modified
VISTA ODBC You are logged on with non-administrative privileges
SYSTEM DSNs could not be created
You are logged on with non-Administrative privledges
You are logged on with non-Administrative privileges
System DSNs non-Administative privileges
System DSNs non-Administrative privileges
Access 2007 System DSNs non-Administrative privileges
ODBC System DSNs VISTA
MICROSOFT VISTA ODBC System DSNs
MICROSOFT VISTA data access components 64 bit
download microsoft data access components 64 bit
mICROSOFT VISTA ACCESS 2007 ODBC 64 BIT

 

[a a r o n _ k e m p f]

have you tried enabling the content?
It just sounds to me like you're Windows won't pass your user Token to
SQL Server (I assume you're trying to use Windows Authentication).

I use Access Data Projects on X64 Vista all the time-- but I sometimes
need to use SQL Authentication (I think that UAC has something to do
with it)

 

[Safety Man]

========================================DJL
I am not quite sure what you mean by "enabling the content"....but I am
starting to parse through other threads about a 32 bit ODBC which may be on a
64 bit OS...

Scenario: I can open the mdb file or create a new MS 2007 native database
and create a new linked table....but when I tried to find the ODBC DSN I
created (previously), it does not show up on the ODBC Datasources. So what I
am presumming is ACCESS 2007 may be using the 32 bit ODBC datasources. But
the OS also states I do not have administrative privledges to create a system
DSN on the ODBC Popup windows(while in ACCESS 2007 linked table Q&A). I will
keep drilling down until I get a complete answer and solution. Already
searched the internet for the answer...none of my error messages (shown
below) guided me to an answer.

THIS IS THE THREAD I FOUND (Can not test until tommorrow)
http://www.microsoft.com/communitie...&p=1&tid=45f9fd0e-31af-4d8d-a094-0fc9eb9cc246

32-bit applications get to use 32-bit ODBC drivers.
64-bit applications get to use 64-bit ODBC drivers.

There's a matching ODBC Administrator for each, which can only see the
relevant drivers too. "Data Sources (ODBC)" from Administrative Tools on
an x64 client runs the 64-bit Administrator - the 32-bit one is in the
sysWOW64 folder.

========================================DJL

 

[a a r o n _ k e m p f]

re:
A potential security concern has been identified - this file might
contain
unsafe content that could harm your computer. Warning it is not
possible to
determine that this content cam from a trustworthy source.

solution:
uh add this path to trusted source or something along those lines;
this should fix your NT AUthentication problem

 

[Sylvain Lafontaine]

For Access running on a 64 bit platform, you must use the 32 bit version of
the ODBCCAD32 program to create your DSNs because Access run under the 32
bit emulation mode (WOW64, don't ask my why it's called WOW64 instead of
WOW32) and can only access registries living on this side of the fence:

Windows\syswow64\odbccad32.exe

 

[Safety Man]

==================================DougLubey
Thanks, you are my hero..This did work for creating the ODBC connection. It
is
strange microsoft did not decide to place the ODBC 32 bit program icon in the
administrative tools right along side the 64 bit program. But anyways it
worked.


As for the other error "enabling the content".
Go to the Office Button (start menu of Access-left hand corner).
Look at the very bottom of the drop down list for "Access Options"
click "Access Options"
Click "Trust Center"(left menu)
Click "Trust Center Settings" (right side of the pop-up window)
Click "Trusted Locations" (left menu)
Click "Add new location" (bottom)
Add the location of where your MDB /MDE file will be running from and if you
need to make sure you click "Trust all sub directories".

Thanks again for the input, it felt good to come in and get this out of the
way today.

-Doug Lubey of Louisiana





==================================DougLubey

 

[a a r o n _ k e m p f]

wow. kudos, I wish I had known about that a couple of years back..

Honestly, thanks!

-Aaron