This simple example program illustrates how VEE can use Microsoft ADO (rev 2.1) Automation Server for integration with SQL Server 7.0 databases.  SQL Server 7.0 must be available on a remote server or on this system as specified in the Server field.  Specify (local) as server if VEE and SQL Server is running on same PC.

The program use SQL's pubs example database by default and:

• Lists all databases on SQL server by reading the Catalog Schema
• Finds all tables in one database (pubs) by reading the Tables Schema
• Allow execution of SQL querys
• Allow viewíng of tables
• Traps ADO errors from SQL Server

This example program contains a Multiple Selection object allowing the user to make one or more selections from an input
list. VEE's standard selection object only allow single item selection.

1. The import of API functions (Function ImportLib)
2. The creation of global constants on runtime from a string array (Function CreateGlobals)
3. The way to find the Window handle of the current VEE application and to change the attributes of the window:
   1. Stay on top
   2. Allow resizing
   3. Show system menu
   4. minimize box enabled/disabled
   5. maximize box enabled/disabled
   6. Hide the entire VEE program for a specified amount of time

Contributed by Georg Nied eMail:info@gn-software.de

Submitted by Juan Carlos Martín Castillejos

This include file has been modified to work the Agilent VEE Import Library object to support the NIDAQ32.DLL.

This modified version is based on the 6.6 version of NI-DAQ.

Return Binary Numbers in Measurement7.0 7.0 The binary (B) format transmits data in measurement units, as binary numbers. This format provides the fastest data transfer and requires the least amount of memory to store data. Each data point is transferred in binary as two 8-bit bytes; the most significant byte is sent first, followed by the least significant byte. Binary data can also be easily converted into measurement data. If speed and memory are important considerations, you may prefer B-format to P-format.  Unlike A-block and I-block formats, the B-format does not send a header. The data is sent immediately, and the end-or-identify message (EOI) is sent with the last byte.

Return Indefinite Block-Data Fields in Measurement Units.  Very similar to A-block format, the I-block format transmits data in measurement units as binary numbers in an indefinite block-data field of unknown size. Each data point is sent as two 8-bit bytes; the most7.0 significant byte is sent first, followed by the least significant byte. The I-block format also transfers a header before the trace data. The header is comprised of ASCII characters "#", and "I".

Return Decimal Numbers in Measurement Units (output only).  The measurement units (M) format transfers trace data as ASCII integer values in measurement units, which is the internal format used by the spectrum analyzer. See Figure 5-8 on page 305. The displayed amplitude of each element falls on one of 601 vertical points (with the 601st equal to the reference level). For example, the peak of the signal in Figure 5-8 on page 305 is equal to -10 dBm, or one division below the reference level. This is equal to 540 measurement units (600 measurement units at the reference level, less 60 measurement units for one division down, equals 540 measurement units). There are also ten additional points of overrange. Measurement units range from 0 to 610.  A line feed (ASCII code 10) follows data output. The end-or-identify message (EOI) is sent with a line feed.  The M-format is faster than the P-format, but most applications will require computer conversion to parameter units. Also, because the M-format transfers data as ASCII characters, the data can be viewed directly.

TDF P: Return7.0 Decimal Numbers in Parameter Units The real number, or "P" format allows you to receive or send data as7.0 ASCII decimal values in real-number (parameter) units. This is the7.0 default format when the instrument is turned on, and when instrument7.0 preset (IP) is activated. Numbers are in dBm, dBmV, dBmV, volts, or7.0 watts, as determined using the amplitude units (AUNITS) command.7.0 Default units are volts for linear trace information, and dBm for7.0 logarithmic trace information.7.0 A line feed (ASCII code 10) follows data output. The end-or-identify7.0 message (EOI) is sent with a line feed.7.0 NOTE When using the P-format, be sure to include amplitude units with the7.0 trace data using the AUNITS command.7.0 Real-number data can be an advantage if you wish to use the data later7.0 in a program. However, data transfers using P-format tend to be slow7.0 and require more storage memory (approximately 1200 bytes for binary7.0 and 4800 bytes for real numbers). In some cases, P-format can take up7.0 to four times the amount of controller memory compared to binary7.0 format.

7.0 TDF B enables the binary format. With the binary format, the marker or trace data is transferred as bytes. Of all the trace data formats, TDF B transfers trace data the fastest. The setting of the MDS command determines whether the trace data is transferred as one or two 8-bit bytes.7.0 NOTE : This example utilizes the MDS B (Measurement Data Size) as BYTE. Transferring a single byte (8-bits) per data point. When transferring trace data, MDS B transfers trace data the faster than MDS W because only 401 bytes are transferred. Because MDS B combines two bytes into one byte, some resolution is lost. 

TDF B enables the binary format. With the binary format, the marker or trace data is transferred as bytes. Of all the trace data formats, TDF B transfers trace data the fastest. The setting of the MDS command determines whether the trace data is transferred as one or two 8-bit bytes.7.0 NOTE : This example utilizes the MDS W (Measurement Data Size) as WORD. Transferring a  word of 2 bytes (8 bits each).per data point. MDS W transfers  trace data with no loss of resolution.

7.0 TDF I is the I-block data format. With the I-block data format, trace data must7.0 be preceded by “#,” and “I.” The setting of the MDS command determines whether the trace7.0 data is transferred as one or two g-bit bytes. Unlike using the A-block format, you do not7.0 provide the number of data bytes when sending trace data back to the spectrum analyzer.

7.0 TDF M is the measurement data format. The measurement data format transfers7.0 trace data in measurement units, and the measurement data can range from -32768 to7.0 + 32767.

Provides an outline for a method to use the 8510 Pass Thru functionality.

Once acquired the temp.plt file can be viewed via any compatible HPGL file viewer. Note newer versions of Microsoft Office products by default do not include the HPGL viewer. Visit Microsoft's website and search on hpgl 32 bit for downloads that can enable HPGL file imports into Microsoft Word and/or Microsoft Excel.

The application is intended to be executed on 8711C, 8712C, 8713C, 8714C and the entire 871xET/ES vector network analyzer families. The program is broken into a main, two user objects, and one user function. The user object "getLearnString" acquires the learnstring and stores the data to text file, 'C:\learnData.txt". This object has it's own notes detailing operation and execution.  The user object "sendLearnStringOut" queries the learn string data from the file 'C:\learnData.txt" and then writes the bytes into the analyzer thus recalling the learnString State. This object has it's own notes detailing operation and execution.  The "err_check" user function provides a means of confirming that no errors are caused during the program execution. The OK buttons allow the user to configure the analyzer, acquire the learnstring, reset analyzer (to a preset) and then resend the acquired learnstring, confirming proper operation.

Use the OUTPLIML command to extract the  stimulus and marker data. NOTE the LIMIT test  FUNCTION is NOT on! The command provides a means to extract the frequency points. 

Note that marker data and the validity of the data is a  function of the analyzers DISPLAY FORMAT. The first value is the marker reading; the second value may or may not be valid as a function of the DISPLAY FORMAT; the third value is the STIMULUS (frequency or time). For full details refer to the 8753/8720 Programmer's Guide Marker Data  section. For this example the FORMAT is LOG MAG, per the manual the second marker value is "insignificant", a.k.a. a place holder, or equivalently JUNK

This application has been tested with the 4395A combination analyzers. The application will catalog the INTERNAL MEMORY  and parse all saved files of type state (as indicated by "*.STA" file type). Once the file list has been created, the  Agilent VEE application will extract all the *.STA files to the external controller. The *.STA files are binary files which can be sent BACK to the 4395A (either via the PC and  VEE, or via 3.5" floppy).

The program queries the instrument(s) for the FORMATTED data trace as a "FORM4"(ascii) data transfer.  The data trace array size is automatically determined from the queried number of points (a.k.a. "no_poin") and then passed to the real_32 array variable. The program outlines some other Agilent VEE features such as querying the trace START Frequency, STOP frequency and NUMBER of POINTS, and then passing these to a linRamp function (embedded in Agilent VEE) in order to AUTOMATICALLY create the frequency points for each data value.  Another feature is the capability to create X-vs-Y plots for displaying the frequency/amplitude data extracted from the analyzer. As a final note the minimum and maximum data values are easily extracted and displayed via Agilent VEE. 

Outlines methods to acquire Impedance, Phase, Parallel Capacitance, Parallel Conductance, in both FORMATTED display trace data and REAL and IMAGINARY data trace formats.

ENA_Average_SPOLL.vee