T
Trent Shirley
My company uses an Outlook form for processing new hire requests.
After entering data into this form they click a button which launches a
Calendar Entry form and it prefills the form fields with the new hire form
data.
The calendar form creates an entry to the calendar and then writes the data
to an Access database.
The database was in Access 97 and it worked fine but the company is pushing
for all older databases to be upgraded.
The database was converted successfully to 2000 and the Calendar Entry form
needed to have the DAO.DBEngine entry updated to .36 (from .35) to allow it
to connect to the 2000 version of the database.
The Calendar form works perfectly, taking the data and writing it to
calendar and the database but....
The problem.
When the new hire form calls the calendar form it will execute normally but
when the client tries to exit the new hire form it causes the "Outlook.exe
has generated errors and will be closed...." message and boots the client
out of Outlook.
The forms work perfectly with Access 2000 and the only script change is the
DAO.DBEngine.36.
I suspect the opening the DAO connection to the database in the 36 version
is causing a conflict or instability that only manifests when the new hire
form tries to continue processing data but cannot track down what it is. I
am only recently familiar with Outlook forms and am hoping this problem is
more readily apparent to the experts here in the newsgroups.
Help???
After entering data into this form they click a button which launches a
Calendar Entry form and it prefills the form fields with the new hire form
data.
The calendar form creates an entry to the calendar and then writes the data
to an Access database.
The database was in Access 97 and it worked fine but the company is pushing
for all older databases to be upgraded.
The database was converted successfully to 2000 and the Calendar Entry form
needed to have the DAO.DBEngine entry updated to .36 (from .35) to allow it
to connect to the 2000 version of the database.
The Calendar form works perfectly, taking the data and writing it to
calendar and the database but....
The problem.
When the new hire form calls the calendar form it will execute normally but
when the client tries to exit the new hire form it causes the "Outlook.exe
has generated errors and will be closed...." message and boots the client
out of Outlook.
The forms work perfectly with Access 2000 and the only script change is the
DAO.DBEngine.36.
I suspect the opening the DAO connection to the database in the 36 version
is causing a conflict or instability that only manifests when the new hire
form tries to continue processing data but cannot track down what it is. I
am only recently familiar with Outlook forms and am hoping this problem is
more readily apparent to the experts here in the newsgroups.
Help???