IADS Configuration Interface COM Interface
patri...@dfrc.nasa.gov
Thanks.
Pat
I'm planing on updating this for 5.0
So far I've just been overwriting the libarry on the download site -
perhaps I need to keep versions ?
patri...@dfrc.nasa.gov
I think it would be good to keep versions. I don't foresee using 5.x
anytime soon for me.
Is it possible to have 2 versions of IADS installed on a client?
(3.4.7 and 4.3)
Thanks.
Pat
read in a 4.0 or 5.0 config - but it always saves out the most current
version - which will work if I post mutiple versions - Ok I'll put it
on my list- I'll go back and post previous ones - I think this
interface came out around the 3.4.7 timeframe. The nice part is if you
create 3.4.7 configs - they will be forward converted by the IADS
system.
2) I'm not the install builder - more a question for Mike Jones - but
I'm 99.9% sure only one verson of IADS can be installed on a single
machine ?
patri...@dfrc.nasa.gov
object with .NET 1.1 using C#?
Have you done it?
Thanks.
Jim Bretz
in .Net and we managed to get everything working ok.
I imagine it would be Ok, but you might want to first build a simple example
and test it out. Also, the steps would be pretty similar to what Terry did
to create an ActiveX control in .Net:
http://www.symvionics.com/products/iads/Downloads/dotnetactivexcontrol.zip
Has anyone else done this yet?? If not, I could give it a shot...
Jim
Pat
I've upgraded the IADS Configuration Interface and uploaded to our Web
site. This upgrade can be used to Open or Create various versions of
the config file, including: 3.4.5, 3.4.7, 4.0, 4.1,4.2,4.3,4.4,4.5 and
5.0. Please note that I changed the inteface by changing the "Version"
method - it now uses an integer version number, 3, 4, or 5. Here is
how they line up:
Version 3 - 3.4.5, 3.4.7
Version 4 - 4.0 to 4.5
Version 5 - 5.0
So if you download this you will need to recompile the IDL.
How does it work ?
If you open a Version 3 config it will also create the a version 3
config, same for Version 4 and 5. You can also set the Version before
the Create and upgrade a config from from a previous version. For
example:
// Open a Version 3 config
// The Open call set the version internally
// Now write it out as a Version 5 config
printf("\n*\n* Create new configuration file called:
'NewConfigV3.txt'\n*\n" ) ;
gConfig->put_Version(5) ;
if( gConfig->Create(L"NewConfigV3.txt", VARIANT_TRUE) != S_OK )
{
printf("** Error creating new configuration file\n" ) ; shutdown()
;
}
Please note that the Post Test Data Sever and the CDS will both forward
convert a config - so this may not really be needed.
I do not believe we have any customers that are using config files
before Version 3(3.4.5) - but if so please let me know
-Pat
patri...@dfrc.nasa.gov
I am attempting to use the 'IadsConfigInterface.dll' from within
C#(2003). I am able to consume the DLL and VS creates the interop for
me (Interop.IADSCONFIGINTERFACELib).
When I instantiate an object (IADSCONFIGINTERFACELib.IadsConfigClass
oIADSConfig = new IADSCONFIGINTERFACELib.IadsConfigClass();)
intellisense shows me the methods that are available, but when I
compile the project and try to create the object the IDE returns:
Additional information: COM object with CLSID
{E4A93884-D3AB-4D7F-ADCE-B6AA967587AB} is either not valid or not
registered.
My system is running IADS 3.4.7 (Client only). Do I still need have
IADS 4.x or greater in order for this to work?
also..
When I used the earlier download of the 'IADSCONFIGTESTERS.ZIP' I was
able to compile and get an executable. The executable failed with
'Unable to create the IadsConfig object ?' which I contributed to not
haveing IADS 4.x installed. In this latest download it appers (and I
very well could be wrong) that some files are missing? Mainly the
'IadsConfigInterface.h'. Any help appreciated. Thanks.
-Patrick-
PS:
After rereading your post I am suspecting I still need to have IADS 4.x
installed. This update only allows you to modify older config files.
Pat
Make sure you register the DLL ?
The zip that you download is self contained. It has within it the
IadsConfigInterface.dll, test program, and sample files - it is not
dependent on any version of IADS. You should be able to register the
dll, compile the test program, and run it. I've included configuration
file versions for each that are supported, pfConfig3.0, pfConfig4.0,
and pfCOnfig5.0. Perhaps it's a VS7/C# issue, I'm still using VS6 for
this project. Although other VS6 DLLs work just fine with executables
that I compiled in VS7, I"m using C++ though ?
I suggest you get the test program running and we can take it from
there. If I get a chance I'll compile the test program with VS7
-Pat
Jim Bretz
>{E4A93884-D3AB-4D7F-ADCE-B6AA967587AB} is either not valid or not
>registered.
> Make sure you register the DLL ?
Yep.... I second that...
http://www.devx.com/tips/Tip/14749
Here's another technique to register dlls:
1) Double click on the dll file
2) Select Open with
3) Browse to C:\Windows\system32\regsvr32.exe
4) Check "Always use the selected program..."
5) Click "Ok"
After you complete these steps your dll will be registered... Also, if you
ever need to register another dll, simply double click on the dll file and
you're done ;)
Jim
----- Original Message -----
From: "Pat" <p...@iads-soft.com>
To: "IADS" <ia...@googlegroups.com>
Sent: Thursday, May 11, 2006 6:34 AM
Subject: [IADS] Re: IADS Configuration Interface COM Interface
>
patri...@dfrc.nasa.gov
Jim Bretz
Thanks Pat ;)
patri...@dfrc.nasa.gov
If the parameter on the front end (Omega) is upper case and I add the
parameter to the IADS config file in mixed case (using the IADS
client). IADS still picks up the correct FE parameter and shows data
(this is from memory, correct me if I'm mistaken)
When using the COM interface casing matters... (ie: 'PTSI_prod' is not
the same as 'PTSI_PROD' (when using the query method). In the config
file would this then represent two separate parameters?
Currently I am comparing the parameters from out FE to the parameters
in the config file. Our FE has all the parameters as uppercase, but in
IADS they are mixed. Should I just convert the IADS config parameters
to upper for comparison?
Will it matter if I write it back as uppercase? (is 'PTSI_prod' and
'PTSI_PROD' the same thing.
Thanks.
patri...@dfrc.nasa.gov
interface. A query with 'PTSI_prod' and 'PTSI_PROD' return the same
information. I am thinking that IADS is NOT case sensative therefore
'PTSI_prod' and 'PTSI_PROD' are the same parameter. The casing is just
for user readability.
Jim Bretz
> Is IADS case sensitive?
Not in the SQL query... The source code for the SQL engine uses "strcmpi"
(i.e. case insensative compare).
> If the parameter on the front end (Omega) is upper case and I add the
> parameter to the IADS config file in mixed case (using the IADS
> client). IADS still picks up the correct FE parameter and shows data
> (this is from memory, correct me if I'm mistaken)
I hope... It should...
> When using the COM interface casing matters... (ie: 'PTSI_prod' is not
> the same as 'PTSI_PROD' (when using the query method). In the config
> file would this then represent two separate parameters?
Nope... Not according to the query engine..
> Currently I am comparing the parameters from out FE to the parameters
> in the config file. Our FE has all the parameters as uppercase, but in
> IADS they are mixed. Should I just convert the IADS config parameters
> to upper for comparison?
Not necessary..
> Will it matter if I write it back as uppercase? (is 'PTSI_prod' and
> 'PTSI_PROD' the same thing.
Nope..
> Thanks.
No problem ;)
Jim
Jim Bretz
Yep... Sorry I didn't read ahead and already responded... You are correct.
Jim