saving a revised form/report

  • Thread starter Thread starter brandon jackson
  • Start date Start date
B

brandon jackson

I have problems saving a revised form. I found a
technique that seems to resolve the problem but not sure
why it works. The following describes the problem and
solutions tried. Does anyone know why the last procedure
works:

Subject: Re: saving a changed form
From: "Brandon Jackson" <[email protected]> Sent:
7/7/2004 12:38:43 PM




I tried each of these to no avail. I did however stumble
across the follow which allows me save the revised
reports. Any idea why this works?
1. Open the database report in Design View;
2. Right click on the report properties tab;
3. Open the properties box;
4. Click on the Event tab;
5. Go to the first line which reads: On Open....[Event
Procedure] is probably selected;
6. Open the three ... buillder box;
7. Select and delete the contents of the box and close
this box;
8. High light and delete the Event Procedure line if
still present;
9. Add back Event Procedure to the line;
10. Can now save the report;
11. If none of the lines in Event have Event Procedure
selected, add it to a line and then do the remove process.

No idea why this works.

Brandon
 
I would guess that something is corrupted. If you are trying to remove all
code from behind the form or report, try setting its HasModule property to
No, this will completely remove the coding. If you are wanting to keep the
coding, you may try saving the code to text, do the above, compact and
repair the database, then select one of the events, reopen the code window,
and paste the code back in. You'll need to reset each event that has code to
[Event Procedure] on the Events tab.

If that still doesn't work, you can find more information on corruption
here.
http://members.iinet.net.au/~allenbrowne/ser-47.html
http://members.iinet.net.au/~allenbrowne/ser-25.html

--
Wayne Morgan
Microsoft Access MVP


brandon jackson said:
I have problems saving a revised form. I found a
technique that seems to resolve the problem but not sure
why it works. The following describes the problem and
solutions tried. Does anyone know why the last procedure
works:

Subject: Re: saving a changed form
From: "Brandon Jackson" <[email protected]> Sent:
7/7/2004 12:38:43 PM




I tried each of these to no avail. I did however stumble
across the follow which allows me save the revised
reports. Any idea why this works?
1. Open the database report in Design View;
2. Right click on the report properties tab;
3. Open the properties box;
4. Click on the Event tab;
5. Go to the first line which reads: On Open....[Event
Procedure] is probably selected;
6. Open the three ... buillder box;
7. Select and delete the contents of the box and close
this box;
8. High light and delete the Event Procedure line if
still present;
9. Add back Event Procedure to the line;
10. Can now save the report;
11. If none of the lines in Event have Event Procedure
selected, add it to a line and then do the remove process.

No idea why this works.

Brandon
-----Original Message-----
Okay, you certainly have a problem with your old database.

You could try compacting a *copy* of your old database, and see if that
helps.
You could also try turning off its Name AutoCorrect, and compacting again.

Double-check you do not have a procedure that has the same name as a module.
For example, if you have:
Function FooBar()
and you also have a module named FooBar, then rename the module.

Finally, the to check the name of the "project", open a code window, and
look on the Tools menu. You will see:
xxx Properties
where xxx is the name of your project. You can use that menu item to rename
the project if necessary.

If none of that works, it may be possible to export the problem report with
the undocumented SaveToText, and import into the new database with
LoadFromText.
Click to expand...
Click to expand...
 
Back
Top