Hi Guys

I need some advise/help with this one.

My client has an OI system that has client details and related transaction records.

They are getting a call centre software installed/customised from an outside group.

The system is in MS SQL

They need read acces to some of the OI Data.

Choice of Methods would like in order of preference:

1. Direct Acces to OI data

My response was they cant

2. OI to write to a SQL file.

Said most possible (Thats why I am here)

3. Create text file export - daily

That is a breeze.

OK. Assuming #2 is possible, I want to know what is the best way of doing it. I would probably look at an mfs that would monitor file changes for specific data - Easy bit.

How do I access the SQL file.

Where do I find the commands to do it

Where do I start.

If there is another easier alternative, I would love to know it. Maybe an easier ODBC to access that can be accesed also by SQL.

Not sure what version of SQL (Saw the KBs on SQL versions and install and it scared me to death )

Hope you can help

Barry

Barry -

We would suggest you speak with Kyle Amadio at Oryx in Parramatta re his work with a similar SQL requirement.

Optionally call Steve Smith on 0397596719 to discuss further possible solutions for all of the issues you raise.

The Sprezzatura Group

World Leaders in all things RevSoft

Thanks,

I will follow up.

Barry

This sounds like the data warehouse stuff that was taught in the Advanced OI class at RevTech… Mike Ruane taught the class I attended. Perhaps there are some handouts or code samples available, or perhaps they are still offering the same class.

]]data warehouse «

Thanks, I found some info on that, looks like what I am looking for.

Barry

Barry

We have done this for two different clients recently. They both actually have two-way updating between Linear Hash and SQL Server (running one running SQL Server 2000, the other SQL Server 6.5). Both are moving to SQL Server/ASP solutions but need the current OI/Arev systems running alongside for some while so two way updating is required.

The LH to SQL is done via an MFS as you suggested. The row is squirted to SQL Server directly on the WRITE logic. The MFS gives a lot more control than the data warehousing and is also absolutely real-time.

The SQL to LH proces is more complex but involves various SQL Server triggers, LH MFS routine and some polling logic. Works like a dream.

There can be a lot of coding though because Arev/OI are more forgiving of data anomolies than SQL Server.

Email me on Tony.Marler@prosolve.co.uk if you need more details.

Tony

View this thread on the forum...