Wiebe, Try running DPEXP.COM on your DP app which creates the .STE file. Then import it back using DPIMP.COM. It might clean up some corruption that could be affecting your report. If you need help in running DPEXP.COM/DPIMP.COM from the Command prompt, let us know. We'll need to know a few basic points such as what version of Windows you are running, the directories where you keep DP and your database and the DP version you are using.
An .STE file of a database is a very useful and powerful tool. You can open it up in a Text Editor to extract elements of a database and create other similar databases by changing the filename. Once you look at an .STE file you'll get a good idea of your database's structure. The Reports are at the bottom. If DPEXP/DPIMP does not correct the problem, your next option will be to run Ralph Alvy's BIG CLEAN which is explained in his fantastic manual - a version of which can be downloaded from the Users Group. Hope this helps. All the best, Tony -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wiebe Cazemier Sent: Thursday, November 29, 2007 12:24 PM To: [email protected] Subject: [Dataperf] Re: Crash while running report The only possibilities are point 3 and 5, as the other ones are not applicable. However, because this report has worked for years, it's unlikely that those points are the problem. The report generates a file, and the last thing that is written in the file, the point where it crashes, it's trying to print out a date. A date which is exactly the same as one that is printed one line before. Additionally, when I delete the card which contains this date, it still crashes. However, I don't know if this is actually the point where the report crashes, or that the crash happens later on, and that this is the last thing it has the chance to write. What exactly is an STE file BTW? I don't have one. On Thursday 29 November 2007 18:39, Michael Iannantuoni wrote: > Hi Wiebe, > > This is what I have about error 197: > > Error: 197 > > Description > Illegal type in report definition. There is an error in a report. This > can be caused by > 1 modifying the .STR file in an ASCII Editor (P-Edit) and removing > only part of a report, > 2 using the create record through link command and deleting the link, > 3 causing a Report Variable to return a numeric value and trying to > use or print it as if it were an alpha string and vice versa, > 4 deleting a link used by a subreport, > 5 selecting a field in a report then changing the type in the report. > > Solution / Trouble Shooting Steps: > Run DPIMP on backup .STE file. > > Not sure if this gives you any clues. > > Michael _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
