I've migrated the database from SQL Anywhere 6.0 to 12.0. I'm having problems with the numeric format in the newer version.

In my old database, the numbers are inserted without any commas, for example "36001.35", but after the migration, the format becomes "36,001.35", it is disturbing the data output in my application. How can I migrate the data from old database to the new database and keep the same format? Please let me know soon. Thanks.

Edit: I just found out that the format can be controlled from the datawindow source. If I see the source of window in the Powerbuilder, there is format specified format="#, ##0.00", and so I can change the format to format="###0.00". Now my question is, is it the proper way to change the format ?(ie. to Edit the source of each of the datawindow? Or there is some general setting/way to do same thing for whole application at once?

asked 17 Jan '12, 02:38

sam's gravatar image

sam
315141624
accept rate: 0%

edited 17 Jan '12, 06:41

Volker%20Barth's gravatar image

Volker Barth
30.3k301453660

Where do you see that format, in your application or when using ISQL or Sybase Central do display data?

(17 Jan '12, 04:51) Reimer Pods
Replies hidden

@Reimer Pods, I edited the question, please see above. I checked old data in the iSQL while the migrated data in the Sybase Central.

(17 Jan '12, 05:32) sam

The display or edit format should be independent of the representation used by database administration tools. When we switched from ASA9 to SA12, we didn't notice any change in datawindow formatting (PB 9).
Anyway, I think an PowerBuilder newsgroup would be more appropriate for this kind of question (PB Resources)

(17 Jan '12, 06:59) Reimer Pods

I would think that this is merely a formatting issue and does not affect the stored data - as long as you are using a numerical data type instead of text.

AFAIK, newer versions (v10/v11?) of DBISL and Sybase Central display numbers formatted as specified in the user's or system's regional settings - therefore adding the thousand separator. In contrast, older versions (and the current dbisqlc) just display numerical data in the standard SQL format (i.e. just a decimal point). The underlying data are not affected by this difference in displaying numbers.


(Sorry, I can't tell on the PowerBuilder question.)

permanent link

answered 17 Jan '12, 05:55

Volker%20Barth's gravatar image

Volker Barth
30.3k301453660
accept rate: 32%

Since V10, ISQL formats numbers using commas as a thousand separator (it is not a thousand separator from the regional settings). However, it is not a big deal, so I've never made fuss out of it.

(17 Jan '12, 06:30) Dmitri
Replies hidden

Well, at least DBISQL v12 does use localized number formatting - in my case, according to the "de-DE" locale with a point as thousand separator and a decimal comma. - But as you say, no big deal:)

(17 Jan '12, 06:39) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×409
×45
×34
×9
×5

question asked: 17 Jan '12, 02:38

question was seen: 4,704 times

last updated: 17 Jan '12, 06:59