Meeting place for R&R customers and clients to share tips and ideas. Post your questions, messages or problems here.
We upgraded from 9 to 10(build 10.0.012) this past Feb. on our old Novell 4.10 File Server running straight IPX protocol. Had few to no problems with v10. Recently we built a Novell 6.0 Server running straight IP protocol, we simply copied the entire R&R program file folder to an identical tree on the new server. We did not re-install R&R on the clients. We have also implemented Novell^s iPrint printing utility on every workstation. Now, with all workstations attached to the new server, R&R crashes every time we save a file. It saves it but it crashes out and leaves the license lock on. Never happened like this on the old server. We USE the librarian, have always used it and do not want to turn it off. ____Michael Hyland - Harrington Corp.
Here is some what happens behing the scenes info.__When you save a report with the librarian enabled, R&R creates a file named rptspec.txt in the RL subdirectory. It then calls the Visual Foxpro program RLCAT.EXE or RLSCAT.EXE (for SQL) adding the name of the rptspec.txt file as an argument. The cataloger then copies each line of the RPTSPEC.TXT file to a record in the table SPEC.DBF. It then reads each record from the file, processes it and updates the files reports.dbf, rptables.dbf, rptfield.dbf. So the RL directory needs to be accessible and all of these files available for read/write.____You might be able to determine at what point the crash is occuring to see if RPTSPEC.TXT is created and if SPEC.DBF is updated.____You should check for any differences in file permissions and also if R&R is being run from a mapped drive letter or a UNC path and if this is different old vs. new.____Kathleen__R&R Support
Thank you for the response,____Not every PC is crashing upon saving a report. We are experiencing two different types of errors, one is the typical Send and Error Report message that Microsoft pops up, this occurs when we Exit R&R Designer. The other is more ominous, it occurs immediately when someone saves a report, the message box title is:____"reportname.rrw - R&R Xbase:rrw.exe - Application error" then below__The instruction at "0x0052cbb5" referenced memory at "0x2e4c50fb", The memory could not be "read". Click OK to terminiate the program, Click on CANCEL to debug the program.____We reinstalled the Server portion of R&R, then uninstalled the workstation portion on one of the workstations receiving this error above. When we Save on this workstaiton, the RPTSPEC.TXT gets updated but SPEC.DBF does not.____Michael
Yes, we observe this in from some workstations with certain reports, however, we are still crashing and cannot save reports, even new ones...what is causing this crash and how can I solve it?____Michael
[updated:LAST EDITED ON Sep-12-03 AT 11:41 AM (EST)]For more clarity:____We receive ONE or TWO error messages when we attempt to save an R&R report(new or old). BUT if we open an existing R&R report and save it with a DIFFERENT name we only receive the Microsoft Send Error Report message. Neither action updates the Report Catalog, sometimes the RRW file is saved, sometimes it^s not.____We usually receive the standard "Please tell Microsoft about this problem" dialog box. When we click "Don^t Send" we get the more ominous "Application Error" message:____"The instruction at "0x73dd1351" referenced memory at 0x000000004". The memory could not be "read". Click OK to terminate program.______When we do it blows us back to the desktop, does not save report file, does not update catalog.____One some workstations only the second message occurs.____If we save the same report with a NEW name we do not get that second message AND it saves the report file, does not update catalog.____Of course, if I set LIBRARIAN=OFF in the INI files the error messages go away. We have found the librarian extremely useful and needful over the past few years and would like to keep using it.______Michael
[updated:LAST EDITED ON Sep-15-03 AT 02:23 PM (EST)]CORRECTION: When I turn Library=Off in INI files error msgs do NOT go away but only come up in certain reports when I print or preview. They save w/o error msgs. ???? Your assistance & support is greatly needed and appreciated.____Michael