Learn how to a build a cloud-first strategyRegister Now


File vs Machine DSN

Posted on 2007-10-16
Medium Priority
Last Modified: 2008-05-01

I am migrating (upsizing) an Access 2002 Access database to Access 2007. Data is in SQL Server 2000. Has a lot of precise numeric data (16 decimal places). In the old version I used a file dsn for the ODBC link - worked great - no issues having dsns configured onto PCs etc....

When I migrated to Access 2007 (staying with SQL 2000) I created a new file dsn and used the convert functionality to create an accdb file. Numeric data on showed to 2 decimal places. I could format the field to 16, but would show as rounded to 2 deimal places with 14 further zeros!

I have created a machine dsn, and data links happily. I've checked the dsn settings and they are exactly the same. Can anyone explain and/or provide a way to make file dsn work?
Question by:Kelvin Sparks
  • 2
  • 2

Accepted Solution

sweekes283 earned 2000 total points
ID: 20085324
If you compare the settings in the registry here:

To the File DSN here:
C:\Program Files\Common Files\ODBC\Data Sources

You may be able to locate the problem.  You'll need to open the DSN in notepad.  The only other item to look at is the connection strings in Access.  If everything matches up, then I'm not sure where to go from there.

Expert Comment

ID: 20090618
If you'd like, export and post the Registry Branch for that DSN, as well as the text in the .DSN file and I'll see if I can find the discrepancies.

I should ask though - why do you need a File DSN, if the Machine DSN works fine?

If it's just a matter of loading that DSN onto other PC's - I believe you would only need to import that registry data onto the new PCs, and you could even have Access do that for you, if you were feeling adventurous.  
LVL 22

Author Comment

by:Kelvin Sparks
ID: 20090631
Have to check when I'm next at that PC. Have historically used a file dsn - was only a chance thought to try a machine dsn to solve the issue.

Will get back to you in a few hours.


LVL 22

Author Comment

by:Kelvin Sparks
ID: 20091571
Had a look at these two. Absolutely nothing there other than one says driver = SQL Server and the other the path to the SQLSERV32.dll. Both have exactly the same server name, database name, trusted connection. No settings there that would be of use at all.

It's not important which way I go, - more so if I could find out why in terms of building my own knowledgebase. To a degree you did that by showing me the registry side of the machine DSN. Happy to reward for your effort.



Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In Part II of this series, I will discuss how to identify all open instances of Excel and enumerate the workbooks, spreadsheets, and named ranges within each of those instances.
In a use case, a user needs to close an opened report by simply pressing the Escape (Esc) key. This can be done by adding macro code in Report_KeyPress or Report_KeyDown event.
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…
Suggested Courses
Course of the Month20 days, 14 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question