comp.lang.idl-pvwave archive: archive » Re: problem with idl database

Home » Public Forums » archive » Re: problem with idl database

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: problem with idl database [message #53770 is a reply to message #53766]

Tue, 01 May 2007 07:09

codepod
Messages: 19
Registered: March 2006

Junior Member

IDL doesn't really support international (Unicode) characters which
is the cause of this issue. When a recordset object connects to a
table, it defines an anonymous structure that maps to a table record.
When it does this, it uses the field names to build structure tags.
This is what's causing the above error.

Really no work around except to build a new table that uses roman
(English) characters.

-CP

On Apr 27, 8:55 pm, "stin.w...@gmail.com" <stin.w...@gmail.com> wrote:
> hi everyone, i have some problem with idl dababase
>
> i am working on some meteorological data which store in a mssql
> server.
> so i use idldabase connect the database, then use idldbrecordset to
> get desired table.
>
> but something happen. because in my original table ,some record name
> is in chinese. when i process this data , it say something like that
>
> "
> OBJ_NEW: Illegal tag name: 区站号.
> Execution halted at: DRAW_DENGWEN 19 F:\源码\IDL\draw_dengwen.pro
> $MAIN$
>
> "
>
> it seem like that the record name must be english. can anyone help my
> exlain this? or find a way to solve this problem?

Report message to a moderator

[Message index]

		Re: problem with idl database By: Rick Towler on Tue, 01 May 2007 10:29
		Re: problem with idl database By: codepod on Tue, 01 May 2007 07:09
		Re: problem with idl database By: stin.wang on Mon, 07 May 2007 18:52
		Re: problem with idl database By: Rick Towler on Wed, 09 May 2007 17:14

Previous Topic:	Re: How to write IDL log output to a file?
Next Topic:	Object Graphics Code Generator

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 15:09:38 PDT 2025

Total time taken to generate the page: 1.44055 seconds