J
jinjin
I am doing a project migrate an Access 1997 application to Access 2003.
We use Citrix to publish the application.
There is one command Cmd.SendObject (....) to send out emails via
Outlook. In Access 1997, when users fist encounters this command, an
outlook profile creation window will be pop out for users to create
their email profile, ( users need to input exchange server name, user
name...). But when we run the same command in Access2003, no profile
creation window pops out. There is an error mssage 'No profiles have
been created. To create a new profile, use the Mail icon in the Control
Panel.'
In our plan, we don't publish Desktop and Outlook for each users. Then
users will have to call support to create profile for the first time
they want to use this application. There is a lot of support work
overhead.
Is there some code in VBA that I can put in Access2003 that I can lauch
Outlook Profile Creation if the system senses that the user has no
profile in place?
Thanks in advance.
JinJin
We use Citrix to publish the application.
There is one command Cmd.SendObject (....) to send out emails via
Outlook. In Access 1997, when users fist encounters this command, an
outlook profile creation window will be pop out for users to create
their email profile, ( users need to input exchange server name, user
name...). But when we run the same command in Access2003, no profile
creation window pops out. There is an error mssage 'No profiles have
been created. To create a new profile, use the Mail icon in the Control
Panel.'
In our plan, we don't publish Desktop and Outlook for each users. Then
users will have to call support to create profile for the first time
they want to use this application. There is a lot of support work
overhead.
Is there some code in VBA that I can put in Access2003 that I can lauch
Outlook Profile Creation if the system senses that the user has no
profile in place?
Thanks in advance.
JinJin