, , , , , ,

Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

Revelation Reporter doesn't work with OI7 ?? (OpenInsight 32-Bit)

At 26 JAN 2004 09:29:12AM SCarlson wrote:

Do I understand correctly that OI 7 will not allow me to run

Revelation Reporter at all??

I have over 100 reports, most with calculated fields, in Reporter.

If this is the case please let me know ASAP so that I won't upgrade

before redoing these reports…. If I need to set these up for

printing only thru OIPI this will require extensive programming

for all of my calculted fields that I let Reported do for me…

Please advise A.S.A.P.

Reporter has been so nice in throwing together a quick report without programming … I can't believe ya'll just scraped it.

Steve C.


At 26 JAN 2004 10:04AM Mike Ruane wrote:

Steve-

We announced this some months ago- I think we started in April.

We have a new Report Builder tool in the product that will create reports for you without programming as well, although it doesn't support temporary calculated fields.

Please look at the Readme.WRI file for more details, as well as the What's New in OI 7.0 seciotn of the online help.


At 26 JAN 2004 10:41AM SCarlson wrote:

Ouch!


At 26 JAN 2004 12:08PM Jim Vaughan wrote:

I must not be getting emails from Revelation or maybe you have the wrong mailing address for me. I never received any notification that Reporter was to be no more.

Nor was it announced at the user group meetings in Southern California that both you and I attended.

Where did you announce that reporter.exe was being discontinued?


At 26 JAN 2004 01:40PM Mike Ruane wrote:

Jim-

I'm pretty sure I did announce it at the SoCalRug meeting. We've mentioned it many time since- I'm surprised that you're surprised.


At 26 JAN 2004 03:48PM Jim Vaughan wrote:

I took copious notes at the last Southern California Users Group meeting I attended and no mention was made of reporter.exe being discontinued. I also attended the road show in Los Angeles and again no mention was made of reporter.exe being discontinued. One of my colleagues went to the Portsmouth NH road show and he confirms that nothing was mentioned about reporter.exe being discontinued. In fact according to my notes you promised no existing applications would break. If I upgrade to 7 our application will be broken; I can not ship the upgrade to my customers without a working reporter.

In October 2003 I received an email describing "Revelation Software Update - Open Insight 7.0"; it describes all the additions to version 7, but no mention is made of the removal of reporter.exe. In December we renewed 2 works memberships in anticipation of the release of version 7, but did so without the knowledge that a key component upon which our application depends would be scrapped. There is no chance that we heard or saw an announcement from Revelation stating support for reporter would be dropped and that we simply forgot.

We develop and maintain a product that uses reporter.exe as the primary method for producing reports. We have created hundreds of custom reports for our clients and as a result I cannot ship version 7. How would they run their reports?

How do I manage moving forward from this point? If reporter cannot be resurrected I will have to maintain two copies of our product one with reporter.exe (version 4.1.3) and one without (version 7). This in and of itself will be a huge amount of extra work. I will then have to undertake the massive task of re-writing all these reports and one by one upgrade my clients to the new version. We also have clients using reporter.exe to write their own reports, what do I tell these clients?

I cannot believe that you intended to cause me this many problems, I was looking forward to using this release. Now I have no idea if or when I will be able to use it.

What caused the removal of reporter.exe? Is it possible to allow reporter.exe to run under version 7.0?


At 26 JAN 2004 04:13PM Mike Ruane wrote:

Jim-

We didn't purposefully break it, we just don't support it anymore. I had figured that it would still work in 7.0; and it does in some of my versions.

We'll look at this and see what happens. We'll let you know by the end of the week.


At 26 JAN 2004 04:30PM Jim Vaughan wrote:

So it should still work but is no longer supported; that's much better.

I will do some research and see if it not working is in someway unique to my machine.

I look forward to hearing from you towards the end of the week.

If there is anything I can to do help, please call me 310-944-3716


At 26 JAN 2004 06:38PM Donald Bakke wrote:

I honestly don't remember what was said at any particular event but we weren't surprised by the dropping of Reporter. In fact, I seem to recall that Reporter was not supposed to work in 7.0 and that we have known about this for some time.

Mike, I thought that changes made that required elimination of Win98 support were what caused the inability to run Reporter anymore.

Could be wrong on this…

[email protected]

SRP Computer Solutions, Inc.


At 26 JAN 2004 09:55PM Mike Ruane wrote:

Jim-

If you copy a pcdlib.dll from 4.1.3 to your 7.0, does reporter run?

I had it working on the plane tonight.

Thanks


At 27 JAN 2004 08:41AM SCarlson wrote:

Don,

Were you a Beta tester of OI 7.0??

I don't belong to any OI user groups(none around) and couldn't attend

any OI seminar's because of budget constraints. I get all of my

info. from this web site and discussion groups.

I don't ever remember seeing anything about Reporter not being

able to work with OI 7.0. If reporter isn't being "supported"

anymore, i.e. no more upgrades, I could live with that as long as

my current reports worked on OI 7.0 and I could take my time to

reprogram about 100 reports (since my primary function is not a programmer(but been working with Revelation since Rev. G in 1985/86) I figure this will take over a year).

If Reporter has ANY chance of not working after my upgrade I would

need to have OI4.13 and OI 7.0 running on my machine so that I can spend the next year working in OI 7 creating reports while my users

and regular application updates continue in OI 4.13.

Revelation: Can I copy my Dev. OI 4.13 into a separate Directory

on my C: drive, update it to 7.0, and have both able to work??

I.E. I don't want any DLL's or other OI apps. updated by OI 7.0 in my WINDOWS\SYSTEM directory which OI 4.13 needs and therefore won't work.

Thanks… (Please keep us updated on how to keep Reporter working on

OI 7.0)

Steve C.


At 27 JAN 2004 09:17AM Donald Bakke wrote:

Steve,

Yes, we were beta testers. It seems that those who use the Reporter are absolutely convinced that this hasn't been publicized enough. I have to take everyone's word for it. Admittedly we haven't been paying that much attention to the dropping of Reporter because we never used the product due to some significant flaws with it…even when it was supported.

Despite our lack of mourning to see Reporter RIP, I believe Jim Vaughan has a valid point about Revelation's committment to "not break any existing applications". Have you tried Mike's suggestion for trying to get Reporter to work in 7.0?

[email protected]

SRP Computer Solutions, Inc.


At 27 JAN 2004 09:38AM SCarlson wrote:

Don,

I'm going to wait 'til I get an answer to this before I upgrade:

"Revelation: Can I copy my Dev. OI 4.13 into a separate Directory

on my C: drive, update it to 7.0, and have both able to work??

I.E. I don't want any DLL's or other OI apps. updated by OI 7.0 in my WINDOWS\SYSTEM directory which OI 4.13 needs and therefore won't work."

I haven't tried it myself yet since I saw the initial reports that

Reporter didn't work. If the answer to the above ques. is yes, I can

have both running from drive C: (not necessarily at the same time), then I'll let everybody know if my Reporter works or not in 7.0


At 27 JAN 2004 11:11AM Sean FitzSimons wrote:

Steve,

As long as you do not run OI 4.1.3 and OI 7.0 concurrently then you should be OK. If you run them concurrently you are in violation of the developer license and will need to buy another license.

Sean


At 27 JAN 2004 11:27AM SCarlson wrote:

Sean,

The license part:

"As long as you do not run OI 4.1.3 and OI 7.0 concurrently then you should be OK. If you run them concurrently you are in violation of the developer license and will need to buy another license."

is ok with me….I was concerned that the software OI 4.13 might not work because of updated DLL or OCX's , etc. that OI 7.0 creates.

Steve C.


At 27 JAN 2004 11:36AM Donald Bakke wrote:

Sean,

Would you please define concurrently for us? I had been meaning to ask a very similar question to Steve's since we are in a position where some clients are now on OI 7.0 but others cannot be moved yet due to client (i.e. Win98) issues. I suppose this is also the same issue for those clients who are still running OI16.

Thanks,

[email protected]

SRP Computer Solutions, Inc.


At 27 JAN 2004 12:05PM Bob Carten wrote:

Steve

I have both on my machine, jump out of one into the other all day without problems.

Bob


At 27 JAN 2004 12:16PM Jim Vaughan wrote:

No, still get a GPF in DE.DLL or RP.DLL


At 27 JAN 2004 12:17PM SCarlson wrote:

Bob,

Thanks… That's what I was waiting for.

Steve C.


At 27 JAN 2004 12:26PM Jim Vaughan wrote:

BTW I can open reporter.exe it "runs" fine.

However if I then open a report I get an GPF in DE.DLL.

Also if I try and open reporter with a report already open by doing this:

STATUS=UTILITY('RUNWIN',DRIVE():'\REPORTER.EXE /AP=W_TACTIC /UN=W_TACTIC /RP=:REPORT_NAME:' /RE=0 /PV=1 /QU',CALLBACK)

I get an GPF in RP.DLL

All GPFs are preceeded by 3 Could not connect to OI messages.

Then one error has occured then the GPF.

Thanks for all the help.


At 27 JAN 2004 02:28PM Sean FitzSimons wrote:

Jim,

Please email me at [email protected]. I may have a fix.

Thanks,

Sean


At 27 JAN 2004 02:41PM Jim Vaughan wrote:

Will do.


At 27 JAN 2004 03:07PM Jim Vaughan wrote:

The fix works, Yeaaaaaa.

Thanks guys; you are the best.

View this thread on the Works forum...