I now understand that the reason for datasets only populating with data (the magic number of 6 rows), even though the dataset contains the correct number of rows (e.g. 205 with rows 7 thru 205 being empty except for the appropriate number of @FM's) is due to WIN 95 not 'supporting' Thunking.

My major concern is 'Is there some way to work around this?'

I programatically instantiate the connection and dataset objects then build, set and execute the dataset Select script. Then, with the dataset active, I fire the popup.

What I have found is that this problem is not isolated to the popup, but the dataset itself only contains 6 populated rows with the rest being empty.

I have clients who are using Client Access, Rhumba, SNA Server etc. to provide access to their AS/400 based tables, and telling them that they must either:

1) Install the 16-bit versions of these programs, solely for their

   OI applications

OR

2) Switch all of the workstations where these apps will be run from 

   WIN 95 to NT

is not going to sit well with their IS groups.

Please tell me that there is a third option available to make this work. I would greatly appreciate any feed back, assistance, options etc. on this topic.

Don Shaw

dshaw@megamationsystems.com

Don,

I'm assuming that you are referring to thunking as it regards to ODBC operations. If this is the case, you should be able to find 16bit ODBC drivers that support the tables you wish to read, without having to install the entire 16-bit version of an application.

Alternatively, you could install the 16-bit version of the ODBC drivers on a single test-system, and look at its configuration in the ODBC.ini file. I might be off-base in this, but I believe you can then just copy the referenced file(s) (and appropriate ODBC.INI entries) over to the machine you wish to be able to use the driver with.

-Scott

Revelation

View this thread on the forum...