• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 477
  • Last Modified:

VB, SQL and German Regional Settings

I'm using vb5 and my regional settings are German. When look into my SQL table the format is correctly sown, with . as the thousand separator and coma as the decimal separator. Why does my recordset return the numbers in the english format? i.e 1,000.00
instead of 1.000,00.
This results in funny results when i add them up. Can anyone help?
0
tiseffies
Asked:
tiseffies
  • 7
  • 3
1 Solution
 
chaniewskimCommented:
Check your ODBC data source. There is an option 'Use regional settings when outputting currency, numbers, dates and times' it's on 4th page of datasource configuration wizard.
0
 
tiseffiesAuthor Commented:
I followed your instructions, and got an error when accessing a field returned from a recordset. The field is of money data type. I set the language on the SQL Server to German, and my regional settings to German. It all should be compatible now..Any ideas would be appreciated

Here is the error:
Run-time error 0:
01S00 [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute

0
 
tiseffiesAuthor Commented:
P.S. Numeric data type works..don't know why money is a problem
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
tiseffiesAuthor Commented:
I realise that ADO fixes the problem...but that is a very big change for me to perform at the moment......
0
 
chaniewskimCommented:
Say, is that error occuring exactly when you access that field?
Could you provide a fragment of code?
0
 
tiseffiesAuthor Commented:
sure. i have also been looking into sql odbc driver patches but no luck yet...
i set the odbc connection
  Set gcnMain = DBEngine.Workspaces("Main").OpenConnection("Main", dbDriverNoPrompt, False, gsODBCConnectString$)

gsODBCConnectString$ = Connect=ODBC;DSN=my_dsn;Database=my_db;UID=sa;PWD=;LoginTimeout=10

then i open a recordset (DAO 3.6)
Set msnTable = gcnMain.OpenRecordset("select * from mytable", dbOpenSnapshot)

then i access the fields:
sTemp = msnTable!numeric_field
sTemp = msnTable!money_field

when i get to line 1 numeric_field...i get the value, line 2 i get the error

I suspect that during the odbc connection it ignores the problem accessing this value, bypasses it somehow, and then only complains when i try to access it.
I also tried using cast in my sql say to numeric but then i lose the money data type's functionality anyway, and i have to repeat that everywhere in the code (or schema) which i don't want.
0
 
chaniewskimCommented:
Sorry... I have no idea :(
0
 
tiseffiesAuthor Commented:
It's ok . I've emailed Microsoft about it too, but they haven't gotten back to me either :(
Thanks for trying :-)
Cheers

Anybody else any ideas?
0
 
tiseffiesAuthor Commented:
I have found the answer to my problem.
The option on the odbc unfortunately caused some conflict when i had the default language set to German in SQL. If i leave the odbc unchecked, and the German default language, and convert my numeric data type to decimal (functionally the same) i overcome the problems I had.
Thanks to everyone who attempted to help.
0
 
tiseffiesAuthor Commented:
Correction I don't need to set the server to German either now. It will still work, just reads the Regional Settings (i must have mixed up as part of my testing). Numeric still has to be converted Decimal which is functionally the same to SQL.
0
 
PashaModCommented:
Closed, 500 points refunded.
PashaMod
Community Support Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now