GUIDO22
Registered User.
- Local time
- Today, 10:02
- Joined
- Nov 2, 2003
- Messages
- 515
I have a report that is showing hashes in fields where the content is truncated.
I modify the report and change the text box width.
I can re-open in Design mode if I chose to after Save. But when i attempt to open the report in Form view, the report wont open.. cursor briefly suggests something is happening but the report fails to load. If I go to delete the form - so that I can import from my backup - Access says it cant delete it while the Report file is open (or equivalent) - despite the Report file not being open or visible...
Why is a simple modification causing this issue - figuring this was a one off I closed Access, reopened and deleted the Report, imported a fresh copy from the backup... checked it worked - then made the change to the report text boxes again - ran it, same problem.. report wont load...
Any ideas people... ? Thanks
======
I have done some further tests and it doesn't matter how 'insignificant' the modification to the report... even moving a single text field a few millimetres causes the above / erroneous operation of the report...
I have also Compacted & Repaired the database (which is a split d/base : front end and back end) - makes no difference, problem still persists...
I modify the report and change the text box width.
I can re-open in Design mode if I chose to after Save. But when i attempt to open the report in Form view, the report wont open.. cursor briefly suggests something is happening but the report fails to load. If I go to delete the form - so that I can import from my backup - Access says it cant delete it while the Report file is open (or equivalent) - despite the Report file not being open or visible...
Why is a simple modification causing this issue - figuring this was a one off I closed Access, reopened and deleted the Report, imported a fresh copy from the backup... checked it worked - then made the change to the report text boxes again - ran it, same problem.. report wont load...
Any ideas people... ? Thanks
======
I have done some further tests and it doesn't matter how 'insignificant' the modification to the report... even moving a single text field a few millimetres causes the above / erroneous operation of the report...
I have also Compacted & Repaired the database (which is a split d/base : front end and back end) - makes no difference, problem still persists...
Last edited: