T
Trent Shirley
I have an Outlook form that calls a second form which creates a calendar
entry then sends the form data to an Access database.
When the access database was in Access 97 and the form reference was
DAO.DBEngine.35 everything worked perfectly.
When we converted the database to Access 2000 we had to change to
DAO.DBEngine.36 for the form to work.
Now, the second form that does the calendar and database entries works
perfectly still, but once the user returns to the original form and tries to
exit it will cause Outlook to crash and boot the user out with the
ubiquitous "Outlook.exe has generated errors and will be closed....".
Now, the first form only crashes when two things are true. 1. That the
calendar form was called while in the first form and 2. that some change to
the data in the first form took place and needed to be saved. If no
changes to the first forms data were made it closes fine. If the calendar
form was not called then the form works fine. If the calendar form uses
DAO 3.5 (for Access 97) the first form still works fine.
I have even setup a simple message box in the Item_Close function for the
first form to make certain the script is not locking up. The message box is
the last item before the end of the function and it executes then Outlook
crashes.
I cannot find a correlation between the forms that could point to the cause
and the only script change is the DAO reference in the calendar form.
The calendar form works as expected and only the first form has a problem.
The first form (New Hire Request) is in our MAC Mailbox folder, the MAC
Calendar is within that folder and the calendar form is in the calendar
itself.
Could somehow the first form be losing sight of where it is operating so
that when it goes to save changed data it crashes? If no data is changed
and it does not need to save then it closes without a problem.
I have never worked in Outlook forms before but know enough VB Script and
Access database programming so I was given the task of converting the
database to 2000. The calendar form worked perfectly after conversion and
we thought it an success so I put it into production and only later found
out the relationship between the calendar and new hire form. Now I look bad
where before management was pleased. *Sigh*
Any help? Please?
I have posted to a couple of groups with similar details but have not
received any responses. I have scoured the web and the groups but cannot
find anything that appears to be relevant to my problem.
entry then sends the form data to an Access database.
When the access database was in Access 97 and the form reference was
DAO.DBEngine.35 everything worked perfectly.
When we converted the database to Access 2000 we had to change to
DAO.DBEngine.36 for the form to work.
Now, the second form that does the calendar and database entries works
perfectly still, but once the user returns to the original form and tries to
exit it will cause Outlook to crash and boot the user out with the
ubiquitous "Outlook.exe has generated errors and will be closed....".
Now, the first form only crashes when two things are true. 1. That the
calendar form was called while in the first form and 2. that some change to
the data in the first form took place and needed to be saved. If no
changes to the first forms data were made it closes fine. If the calendar
form was not called then the form works fine. If the calendar form uses
DAO 3.5 (for Access 97) the first form still works fine.
I have even setup a simple message box in the Item_Close function for the
first form to make certain the script is not locking up. The message box is
the last item before the end of the function and it executes then Outlook
crashes.
I cannot find a correlation between the forms that could point to the cause
and the only script change is the DAO reference in the calendar form.
The calendar form works as expected and only the first form has a problem.
The first form (New Hire Request) is in our MAC Mailbox folder, the MAC
Calendar is within that folder and the calendar form is in the calendar
itself.
Could somehow the first form be losing sight of where it is operating so
that when it goes to save changed data it crashes? If no data is changed
and it does not need to save then it closes without a problem.
I have never worked in Outlook forms before but know enough VB Script and
Access database programming so I was given the task of converting the
database to 2000. The calendar form worked perfectly after conversion and
we thought it an success so I put it into production and only later found
out the relationship between the calendar and new hire form. Now I look bad
where before management was pleased. *Sigh*
Any help? Please?
I have posted to a couple of groups with similar details but have not
received any responses. I have scoured the web and the groups but cannot
find anything that appears to be relevant to my problem.