OpenInsight Evaluation version 4.1.1

Has anyone had any success implementing an OI DataSet in version 4.X connecting to a Microsoft SQL-2000 database table?

The OI Connection Entity works well . . I can have successfully connected and can query the MS-SQL database tables.

Then . . I set up an OI DataSet Entity.

1. From the ?General Tab? I entered a Title and selected the Data Source from the drop down the data source that was created via the Connection Entity routine was my selection. The following message is returned:

   Connection Succeeded 

   MicrosoftODBC SQL Server DriverSQL Server changed data base context to ?the data source name?

   MicrosoftODBC SQL Server DriverSQL Server changed language setting to ?us_english?

2. From the ?Scripts Tab? I pressed the ?Use Table?? button. The following message was returned . . .

   Connection Failed

   Functionality not supported

This did not allow me to select a table nor define table columns. So I really don?t have much of a DataSet Entity. I couldn?t go any further using the DataSet Entity function.

Is this a bug or am I doing something incorrect?

Any help will be very much appreciated.

Chris Guido

Integre

We have been unable to establish datasets to ANY back end source without hand coding them. It seems that the functionality to return table/column lists has changed or something.

The Sprezzatura Group

World Leaders in all things RevSoft

Chris,

There does seem to be a problem with Datasets (though i haven't tested against 4.1.1 as we like to sling the code ourselves).

I believe rti is aware of this and it is on the list.

dsig@sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 503-639-4240

OS: Win2k sp2 (5.00.2195)

OI: 4.1

Correct- we've been poking at this, and should have an answer soon.

Mike

Chris,

There is a workaround. Instead of manually creating a DataSet entity, if you create a Data Warehouse procedure and then run it, the procedure will create a DataSet entity called WP_. After that, you can create a form against the table using the data set entity.

Ira

Are you sure of this? The reason I ask is that the first time I had a problem with datasets is when I was testing warehousing.

Like i said before I use XO Querys (xo-on xo-off makes me think of the Karate Kid . I was just trying to dump some data quickly and used warehousing and it said it was moving data .. but nothing happened. I then played with datasets and had problems.

dsig@sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 503-639-4240

OS: Win2k sp2 (5.00.2195)

OI: 4.1

Dave,

This is how I got OI 4.1.1 to create a DataSet for a LH table using the Data Warehouse.

1) Create an ODBC connection to SQL Server 2000, to the database where the data warehouse tables will reside.

2) Select Tools-Create Warehouse Procedure.

3) Select the LH table you want to create the DataSet for, and click NEXT.

4) Click NEXT to accept the default Number of Tables.

5) Select the primary key field(s) and click NEXT.

6) Click DEFINE to start defining the SQL Server 2000 table for this LH table. Then define the primary key and non-key fields to be "warehoused".

7) The scripts are automatically generated. Review and click FINISH.

8) Click NEXT, enter the warehouse definition name, and click FINISH.

This creates the dataset definition. If you use the menu's File-Open command, and select the List Entities of Type DataSet, you should see a DataSet entity called WP_. If you examine it, you should see the SELECT, INSERT, DELETE, and UPDATE scripts generated.

Admittedly, this is a bit roundabout, but it should save time and possibly be more accurate.

By the way…if I click the Schedule button in the Warehouse Manager, RTP26 drops into the debugger.

Hope this helps.

Ira

Phone: 781-438-6335

email: ikrakow_1999@yahoo.com

OI 4.1.1

OS: Windows XP Home

Computer: Compaq Presario 6000

SQL Server 2000 Personal Edition

Ira,

Sorry, i probably wasn't clear in my comment. Not that WH didn't create the dataset definition .. just that WH didn't work in our testing.

Whether we are using MSSql 2000 or testing against MSAccess all 'transacations' fail to get to the server. It went through the counting but looking at the log every insert fail

This is what started us looking at datasets.

dsig@sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 971-570-2005

OS: Win2k sp2 (5.00.2195)

OI: 4.1.1

PII 300 laptop

View this thread on the forum...