View Full Version : Error
Rafael M Heise
7-Jul-2010, 03:33 PM
This error was throw when the user open the report, I guess:
Could not read data (DataFlex driver), please report this erro to support@dataaccess.eu (1)
But it's not happens everytime. And they are using the MS SQLServer data base.
3517
Vincent Oorsprong
8-Jul-2010, 06:11 AM
Rafael,
Does the report use ODBC or INT files to get to MSSQL Server?
Note that for speed it is advisable to use ODBC.
Rafael M Heise
8-Jul-2010, 08:20 AM
It's using INT files.
Bob Worsley
8-Jul-2010, 08:45 AM
It's using INT files.
For SQL, you really should use an ODBC connection and not the native DF, the speed difference is huge! ODBC is orders of magnitude faster.
Larry R Pint
8-Jul-2010, 09:02 AM
For SQL, you really should use an ODBC connection and not the native DF, the speed difference is huge! ODBC is orders of magnitude faster.
Oh, how times have changed! When ODBC first came out, its performances was SO bad that it was generally agreed that ODBC stood for Oh Don't Bother Connecting.:D:eek:
Bob Worsley
8-Jul-2010, 09:10 AM
Oh, how times have changed! When ODBC first came out, its performances was SO bad that it was generally agreed that ODBC stood for Oh Don't Bother Connecting.:D:eek:
Exactly my initial reaction but Ulbe showed me the error of my way when VRW first came out, so I've become a believer in this case. :cool:
I do remember years ago at some former employer, sales wanted to connect to a mainframe from DF via ODBC and I had the audacity to tell the customer that it would be slow... Got spanked for that one, learned never to tell the truth when in a sales situation!
craigkrum
8-Jul-2010, 10:48 AM
This is an error I get randomly too, but I am using the embedded database. It can happen when I am testing my report and I refresh the report data, but also pops up when reports are run from within my application. Closing the error and trying the report again usually works, but my application is web based and the message pops up on the server, so there is no way for the user to close it and retry the report. Until the error is cleared, VRW will not respond to any other request for a report, so users are stuck until I clear the error myself.
Since it always seems to work on a second try, is there any way to make VRW automatically retry accessing the data itself instead of stopping with an error? I'd hate to have to camp out in front of my server just so I can click the button to clear the error.
Rafael M Heise
8-Jul-2010, 11:52 AM
Maybe you could try to use a try-catch statement... D'oh! There is no try-catch statement! :D
I'm just kidding...
Did you have tried to use the ignore_error method?
Maybe you could use that, cathing the error in you own Error_Object, and if the report throw any error message, you could try print the report again. It's just an ideia.
craigkrum
8-Jul-2010, 12:56 PM
Ah, interesting idea. I will look into that. I think the error comes directly from vrw.exe so I'm not sure if I can put any logic in my application that might catch it, but definetely worth a look.
Rafael M Heise
8-Jul-2010, 01:14 PM
I suggested you to ignore the error because now the VRW is something like a COM object. And as you are using the VRW with a WebApp (I guess), I think you are printing directly in a file and show it up to the user, directly on browser or asking to user download the report file. And as you are oing something like that, maybe ignoring the error and trying to print again can solve your problem.
In my application, we show the report on screen, so we can't do something to ignore the error message, because it appears after popup the report dialog. But maybe in your case you can do that.
craigkrum
8-Jul-2010, 01:43 PM
VRW doesnt work directly with web apps yet, so I have a VDF application running on the server, looking for a file created by the web app that tells it to generate the pdf report. When it sees the file, it calls VRW, like normal, with things set to go directly to a pdf file. The web app then waits for the file to be created and displays it directly on the web page. So it pretty much runs like any other application using VRW, it is just triggered by an event from the web app instead of a keystroke. I'm not sure how the call to VRW is made, but hopefully it will obey and ignore error command.
Hopefully the bright folks at dataaccess will find some way to fix this, but until then, I'll see if there is some way to implement your suggestion. Part of the problem is that the error is so random that it is going to be hard to test it.
Bob Worsley
8-Jul-2010, 01:49 PM
VRW doesnt work directly with web apps yet
Acutally it does. I've been using the VRW API very successfully with my WebApp since RC II.
craigkrum
8-Jul-2010, 01:53 PM
Acutally it does. I've been using the VRW API very successfully with my WebApp since RC II.
That would certainly make things a bit easier. My method was just a hold over from the pre-VRW days using the regular report writer and a PDF print driver. One more thing to look into!
Bob Worsley
8-Jul-2010, 02:00 PM
It's sort of documented, but if you want some code let me know.
craigkrum
8-Jul-2010, 02:07 PM
Sample code would be MUCH appreciated. It's not that I'm lazy, I'm just not that bright :confused:
Thanks
Bob Worsley
8-Jul-2010, 03:29 PM
Sample code would be MUCH appreciated. It's not that I'm lazy, I'm just not that bright :confused:
Thanks
Isn't that Garret's line? :D
Garret Mott
8-Jul-2010, 03:33 PM
Isn't that Garret's line? :D
Nope - I'm not only not very bright, but I'm lazy too!
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.