| Finding a structure in a structure [message #28675] |
Mon, 07 January 2002 13:09  |
timothy.williams
Messages: 20
Registered: October 2001
|
Junior Member |
|
|
I have an application that is using Dataminer to access a database,
one of the functions being to display the tables in the database. So
far, my database has been Oracle on a Sun, where my IDL on a PC. I'm
now migrating over some of the tables to Access on the PC. I now have
a problem because one of my fields has a date in it which was a STRING
before, but in the Access database is the structure
ODBC_SQL_TIMESTAMP. I'm getting an error that structures can't contain
other structures.
My plan now is to write code to convert this structure to a string so
I can put the date in the table widget structure.
How? I can do a tag_names(recordset, /structure_name) and test for
'ODBC_SQL_TIMESTAMP', but I'm not sure how to search through each
member in the database recordset structure. I don't know how to handle
the errors I will have when I call tag_names() with the members that
aren't structures.
Thanks for any help.
|
|
|
|
| Re: Finding a structure in a structure [message #28761 is a reply to message #28675] |
Tue, 08 January 2002 08:47  |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
Tim Williams wrote:
>
> By rectifying this directly in Access, do you mean converting the
> format of the
> field from Date/Time to Text? I tried that, but Access reformatted the
> data from the Medium Date format, which is what I had in the original
> table, to the General Date.
This is not exactly IDL, but...
You have full control over Access date -> string conversion. In fact,
VBA FORMAT function is completely intuilive and can return dates
formatted exactly as you'd like. You can look it up in Access VBA help,
or email me directly because we are about to get flamed for polluting
IDL NG with MS stuf :)
> I don't want to change the format of the
> data, so I guess I have to do I myself. The Access people over here
> say I can't change the way Access converts Dates to Text. (I suppose
> this is another example of Bill making your decisions for you.)
Those people are mistaken, I think. I have not yet seen one thing that
you can't do in Access (except, maybe, making your computer walk over
your desktop) - it is just that you need to dig through a lot of stuff
to find out *how* to do it.
> I don't really know as much as I should about Access, (or Oracle
> either for that mattter), but I'll have databases on both, so I don't
> want to depend on either. It just depends on which database the user
> connects to as to which tables will be available.
I think that for database control and management you will be better off
using Access (as compared with IDL). I don't know Oracle - sorry. IDL
ODBC in my opinion is merely the means for pulling data out of a DB for
processing in IDL. But I find Access very easy to learn - you can have a
simple application up and running in 3-4 days, starting from scratch
(that is, having no pre-existing knowledge of VBA and Access). It is
even faster if you have a sample database to play with. Of course,
advanced stuff and high performance features will come later.
Good luck,
Pavel
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
