Create Appointment Item Outlook 2019 and find by EntryID

Hello,

i want to create an appointment item in outook 2019 (365). After save this item has to be display.

After the display i need this item to work with it, but the instance ends after display.

I start a new outlook "session" to find the item with the EntryID but it end with an -155 error at the last line .... GETITEMFROMID.

Any Idea oder experience about this?

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)
hv_TASKITEM->SET_SUBJECT("TEST")
hv_TASKITEM->SAVE()
hv_TASKITEM->GET_ENTRYID(sv_ENTRYID)
hv_TASKITEM->DISPLAY("TRUE")

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->GET_SESSION(hv_SESSION)
hv_SESSION->GETDEFAULTFOLDER(hv_DEFAULTFOLDER,9)
hv_DEFAULTFOLDER->GET_STOREID(sv_STOREID)
hv_SESSION->GETITEMFROMID(hv_TASKITEM,sv_ENTRYID,sv_STOREID)

THX a lot

Hi Dirk,

could it be you should explicitely use deleteinstance for your first instance before let's code going for the second newinstance?
Or:
you should use another handler to manage two instances in memory without hiccups?

I did not verified these suggestions ... 😉

Regards,
Gianni

Hello,

i want to create an appointment item in outook 2019 (365). After save this item has to be display.

After the display i need this item to work with it, but the instance ends after display.

I start a new outlook "session" to find the item with the EntryID but it end with an -155 error at the last line .... GETITEMFROMID.

Any Idea oder experience about this?

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)
hv_TASKITEM->SET_SUBJECT("TEST")
hv_TASKITEM->SAVE()
hv_TASKITEM->GET_ENTRYID(sv_ENTRYID)
hv_TASKITEM->DISPLAY("TRUE")

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->GET_SESSION(hv_SESSION)
hv_SESSION->GETDEFAULTFOLDER(hv_DEFAULTFOLDER,9)
hv_DEFAULTFOLDER->GET_STOREID(sv_STOREID)
hv_SESSION->GETITEMFROMID(hv_TASKITEM,sv_ENTRYID,sv_STOREID)

THX a lot

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hello,

i want to create an appointment item in outook 2019 (365). After save this item has to be display.

After the display i need this item to work with it, but the instance ends after display.

I start a new outlook "session" to find the item with the EntryID but it end with an -155 error at the last line .... GETITEMFROMID.

Any Idea oder experience about this?

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)
hv_TASKITEM->SET_SUBJECT("TEST")
hv_TASKITEM->SAVE()
hv_TASKITEM->GET_ENTRYID(sv_ENTRYID)
hv_TASKITEM->DISPLAY("TRUE")

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->GET_SESSION(hv_SESSION)
hv_SESSION->GETDEFAULTFOLDER(hv_DEFAULTFOLDER,9)
hv_DEFAULTFOLDER->GET_STOREID(sv_STOREID)
hv_SESSION->GETITEMFROMID(hv_TASKITEM,sv_ENTRYID,sv_STOREID)

THX a lot

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hi Dirk,

I am back to work now and I am checking your code to my repo.

I've used O16_ as a prefix while loading Outlook16 signatures into Uniface repo. So where you have OUTLOOK16_ in mine you will see O16_.

Let's go step by step. I am finding no issue while executing first two instructions:

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)

Now...I am getting -59 (operation does NOT exists) after executing SET_SUBJECT(). The SET_SUBJECT operation is requested into the object given back from previous istruction CREATE_ITEM(). My CREATE_ITEM() operation is giving back a O16__ITEMS object while your should be mapped to a different object; I've executed this query into my Uniface repo:

      select uspecnam from usoper where uspecnam like 'O16_%' and uopernam = 'SET_SUBJECT'

it is giving back components which includes the SET_SUBJECT() operation/method; the result is:

USPECNAM
==================
O16_CONTACTITEM
O16_MAILITEM
O16_SHARINGITEM
O16__CONTACTITEM
O16__MAILITEM
O16__SHARINGITEM
O16__STORAGEITEM

To which of those objects is it mapped your CREATE_ITEM() operation/method?

My bet is for *_MAILITEM... 🙂 If yes, have you already used your signatures to build a sending mail functionality before?

Regards,
Gianni

Hi Dirk,

I am back to work now and I am checking your code to my repo.

I've used O16_ as a prefix while loading Outlook16 signatures into Uniface repo. So where you have OUTLOOK16_ in mine you will see O16_.

Let's go step by step. I am finding no issue while executing first two instructions:

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)

Now...I am getting -59 (operation does NOT exists) after executing SET_SUBJECT(). The SET_SUBJECT operation is requested into the object given back from previous istruction CREATE_ITEM(). My CREATE_ITEM() operation is giving back a O16__ITEMS object while your should be mapped to a different object; I've executed this query into my Uniface repo:

      select uspecnam from usoper where uspecnam like 'O16_%' and uopernam = 'SET_SUBJECT'

it is giving back components which includes the SET_SUBJECT() operation/method; the result is:

USPECNAM
==================
O16_CONTACTITEM
O16_MAILITEM
O16_SHARINGITEM
O16__CONTACTITEM
O16__MAILITEM
O16__SHARINGITEM
O16__STORAGEITEM

To which of those objects is it mapped your CREATE_ITEM() operation/method?

My bet is for *_MAILITEM... 🙂 If yes, have you already used your signatures to build a sending mail functionality before?

Regards,
Gianni

Hi Dirk,

I am back to work now and I am checking your code to my repo.

I've used O16_ as a prefix while loading Outlook16 signatures into Uniface repo. So where you have OUTLOOK16_ in mine you will see O16_.

Let's go step by step. I am finding no issue while executing first two instructions:

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)

Now...I am getting -59 (operation does NOT exists) after executing SET_SUBJECT(). The SET_SUBJECT operation is requested into the object given back from previous istruction CREATE_ITEM(). My CREATE_ITEM() operation is giving back a O16__ITEMS object while your should be mapped to a different object; I've executed this query into my Uniface repo:

      select uspecnam from usoper where uspecnam like 'O16_%' and uopernam = 'SET_SUBJECT'

it is giving back components which includes the SET_SUBJECT() operation/method; the result is:

USPECNAM
==================
O16_CONTACTITEM
O16_MAILITEM
O16_SHARINGITEM
O16__CONTACTITEM
O16__MAILITEM
O16__SHARINGITEM
O16__STORAGEITEM

To which of those objects is it mapped your CREATE_ITEM() operation/method?

My bet is for *_MAILITEM... 🙂 If yes, have you already used your signatures to build a sending mail functionality before?

Regards,
Gianni

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hi Dirk,

I am back to work now and I am checking your code to my repo.

I've used O16_ as a prefix while loading Outlook16 signatures into Uniface repo. So where you have OUTLOOK16_ in mine you will see O16_.

Let's go step by step. I am finding no issue while executing first two instructions:

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)

Now...I am getting -59 (operation does NOT exists) after executing SET_SUBJECT(). The SET_SUBJECT operation is requested into the object given back from previous istruction CREATE_ITEM(). My CREATE_ITEM() operation is giving back a O16__ITEMS object while your should be mapped to a different object; I've executed this query into my Uniface repo:

      select uspecnam from usoper where uspecnam like 'O16_%' and uopernam = 'SET_SUBJECT'

it is giving back components which includes the SET_SUBJECT() operation/method; the result is:

USPECNAM
==================
O16_CONTACTITEM
O16_MAILITEM
O16_SHARINGITEM
O16__CONTACTITEM
O16__MAILITEM
O16__SHARINGITEM
O16__STORAGEITEM

To which of those objects is it mapped your CREATE_ITEM() operation/method?

My bet is for *_MAILITEM... 🙂 If yes, have you already used your signatures to build a sending mail functionality before?

Regards,
Gianni

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hi Dirk,

mmmhhhmmm...

Error -155 is related to newinstance and it is described as:

The description is obviously related to a Uniface component instance but it is applicable with a "grain of salt" to any newinstance.

Few more thoughts:
- are you sure you declared all variables in a proper way?
- any feedback ($status or $result) in the code lines before the one giving error? All expected INOUT or OUT parameters are exiting without any hiccups?
- could it be a timing problem? Try to add a deleteinstance then put a sleep instruction for at least 2-3 seconds before the 2nd new instance.
- Is Outlook on that machine/node already correctly initialized? I mean: opening it interactively does not show any intermediate question screen?

Regards,
Gianni

Hello,

i want to create an appointment item in outook 2019 (365). After save this item has to be display.

After the display i need this item to work with it, but the instance ends after display.

I start a new outlook "session" to find the item with the EntryID but it end with an -155 error at the last line .... GETITEMFROMID.

Any Idea oder experience about this?

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)
hv_TASKITEM->SET_SUBJECT("TEST")
hv_TASKITEM->SAVE()
hv_TASKITEM->GET_ENTRYID(sv_ENTRYID)
hv_TASKITEM->DISPLAY("TRUE")

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->GET_SESSION(hv_SESSION)
hv_SESSION->GETDEFAULTFOLDER(hv_DEFAULTFOLDER,9)
hv_DEFAULTFOLDER->GET_STOREID(sv_STOREID)
hv_SESSION->GETITEMFROMID(hv_TASKITEM,sv_ENTRYID,sv_STOREID)

THX a lot

Hi all,

when I import the Signatures with

/sti /mwr=com /pid Outlook.Application:outlook_

then I can not found any Signatures for Class TaskItem nor Class AppointmentItem

but when I import the Signatures with

/sti /mwr=com "C:\\Program Files\\Microsoft Office\\root\\Office16\\MSOUTL.OLB"

then I will find them as TASKITEM and U_TASKITEM ...

So what is the Difference between the to Statements?

Why can't we use a prefix for the second Statement?

Regards

Norbert

Hi all,

when I import the Signatures with

/sti /mwr=com /pid Outlook.Application:outlook_

then I can not found any Signatures for Class TaskItem nor Class AppointmentItem

but when I import the Signatures with

/sti /mwr=com "C:\\Program Files\\Microsoft Office\\root\\Office16\\MSOUTL.OLB"

then I will find them as TASKITEM and U_TASKITEM ...

So what is the Difference between the to Statements?

Why can't we use a prefix for the second Statement?

Regards

Norbert

Hi all,

when I import the Signatures with

/sti /mwr=com /pid Outlook.Application:outlook_

then I can not found any Signatures for Class TaskItem nor Class AppointmentItem

but when I import the Signatures with

/sti /mwr=com "C:\\Program Files\\Microsoft Office\\root\\Office16\\MSOUTL.OLB"

then I will find them as TASKITEM and U_TASKITEM ...

So what is the Difference between the to Statements?

Why can't we use a prefix for the second Statement?

Regards

Norbert

Hi all,

when I import the Signatures with

/sti /mwr=com /pid Outlook.Application:outlook_

then I can not found any Signatures for Class TaskItem nor Class AppointmentItem

but when I import the Signatures with

/sti /mwr=com "C:\\Program Files\\Microsoft Office\\root\\Office16\\MSOUTL.OLB"

then I will find them as TASKITEM and U_TASKITEM ...

So what is the Difference between the to Statements?

Why can't we use a prefix for the second Statement?

Regards

Norbert

Hi all,

when I import the Signatures with

/sti /mwr=com /pid Outlook.Application:outlook_

then I can not found any Signatures for Class TaskItem nor Class AppointmentItem

but when I import the Signatures with

/sti /mwr=com "C:\\Program Files\\Microsoft Office\\root\\Office16\\MSOUTL.OLB"

then I will find them as TASKITEM and U_TASKITEM ...

So what is the Difference between the to Statements?

Why can't we use a prefix for the second Statement?

Regards

Norbert

Hello,

i want to create an appointment item in outook 2019 (365). After save this item has to be display.

After the display i need this item to work with it, but the instance ends after display.

I start a new outlook "session" to find the item with the EntryID but it end with an -155 error at the last line .... GETITEMFROMID.

Any Idea oder experience about this?

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->CREATEITEM(hv_TASKITEM, 1)
hv_TASKITEM->SET_SUBJECT("TEST")
hv_TASKITEM->SAVE()
hv_TASKITEM->GET_ENTRYID(sv_ENTRYID)
hv_TASKITEM->DISPLAY("TRUE")

newinstance "OUTLOOK16_APPLICATION", hv_APPLICATION
hv_APPLICATION->GET_SESSION(hv_SESSION)
hv_SESSION->GETDEFAULTFOLDER(hv_DEFAULTFOLDER,9)
hv_DEFAULTFOLDER->GET_STOREID(sv_STOREID)
hv_SESSION->GETITEMFROMID(hv_TASKITEM,sv_ENTRYID,sv_STOREID)

THX a lot

Some time ago I've created a little tool for COM (and C) signatures that can be found on Github:

> https://github.com/uniface/tool-development/tree/u9/uniface-sigwiz

In 2015 I even gave a presentation about the tool at the German user conference in Augsburg (https://www.u-b-g.org/tagung/201501/).

I also have a Uniface 10 version of the tool, but it's not yet on Github. I, however can share it if someone is interested.

And the difference between importing the COM signatures using /pid or a type library is as follows:

When /pid is used then Uniface:

• will instantiate the specified COM object and query the API of the running object recursively
• it hereby starts with the object specified by /pid (e.g. Outlook.Application) and then queries every available method or property; when something returns another object then Uniface will try to instantiate that as well an continue to query the API until there's nothing left (so to speak)
• for each identified object a signature is created and for each method or property of that object Uniface will create an operation with its parameters; in case the discovered interface is not compatible with Uniface then this will fail and a warning/error is returned; some data types also default back to string although it might be something different that Uniface does not know or is not clear (e.g. the actual data type of the the returned value depends on how the method/property is called)
• it is possible that not all the available objects are directly accessible through the API of the instantiated object; in some cases just an object is returned without specifying it's actual type or PID; for this Uniface will then create a handle parameter with an UNKNOWN classification

When using the type library then Uniface:

• will read the library file sequentially and creates signatures for the detected objects, methods, properties, ...
• from here on the process is similar to what /pid is doing
• again, when an unspecified object is returned then Uniface create a handle parameter with  an UNKNOWN classification

The above mentioned tool allows you to check all parameters for the UNKNOWN handle classification and from the search result you can open the affected operations. From there you can easily change the classification.

Besides this the tool also allows you to add a prefix to all signatures or rename them in one go (or individually). You also can rename, copy, or move operations. In addition you also can navigate from one signature to another (by double clicking on the handle classification of a parameter). You can also filter the signatures, import, export, or compile them. There's probably more, but that's all I remember at the moment.

I hope this helps.

Some time ago I've created a little tool for COM (and C) signatures that can be found on Github:

> https://github.com/uniface/tool-development/tree/u9/uniface-sigwiz

In 2015 I even gave a presentation about the tool at the German user conference in Augsburg (https://www.u-b-g.org/tagung/201501/).

I also have a Uniface 10 version of the tool, but it's not yet on Github. I, however can share it if someone is interested.

And the difference between importing the COM signatures using /pid or a type library is as follows:

When /pid is used then Uniface:

• will instantiate the specified COM object and query the API of the running object recursively
• it hereby starts with the object specified by /pid (e.g. Outlook.Application) and then queries every available method or property; when something returns another object then Uniface will try to instantiate that as well an continue to query the API until there's nothing left (so to speak)
• for each identified object a signature is created and for each method or property of that object Uniface will create an operation with its parameters; in case the discovered interface is not compatible with Uniface then this will fail and a warning/error is returned; some data types also default back to string although it might be something different that Uniface does not know or is not clear (e.g. the actual data type of the the returned value depends on how the method/property is called)
• it is possible that not all the available objects are directly accessible through the API of the instantiated object; in some cases just an object is returned without specifying it's actual type or PID; for this Uniface will then create a handle parameter with an UNKNOWN classification

When using the type library then Uniface:

• will read the library file sequentially and creates signatures for the detected objects, methods, properties, ...
• from here on the process is similar to what /pid is doing
• again, when an unspecified object is returned then Uniface create a handle parameter with  an UNKNOWN classification

The above mentioned tool allows you to check all parameters for the UNKNOWN handle classification and from the search result you can open the affected operations. From there you can easily change the classification.

Besides this the tool also allows you to add a prefix to all signatures or rename them in one go (or individually). You also can rename, copy, or move operations. In addition you also can navigate from one signature to another (by double clicking on the handle classification of a parameter). You can also filter the signatures, import, export, or compile them. There's probably more, but that's all I remember at the moment.

I hope this helps.

Some time ago I've created a little tool for COM (and C) signatures that can be found on Github:

> https://github.com/uniface/tool-development/tree/u9/uniface-sigwiz

In 2015 I even gave a presentation about the tool at the German user conference in Augsburg (https://www.u-b-g.org/tagung/201501/).

I also have a Uniface 10 version of the tool, but it's not yet on Github. I, however can share it if someone is interested.

And the difference between importing the COM signatures using /pid or a type library is as follows:

When /pid is used then Uniface:

• will instantiate the specified COM object and query the API of the running object recursively
• it hereby starts with the object specified by /pid (e.g. Outlook.Application) and then queries every available method or property; when something returns another object then Uniface will try to instantiate that as well an continue to query the API until there's nothing left (so to speak)
• for each identified object a signature is created and for each method or property of that object Uniface will create an operation with its parameters; in case the discovered interface is not compatible with Uniface then this will fail and a warning/error is returned; some data types also default back to string although it might be something different that Uniface does not know or is not clear (e.g. the actual data type of the the returned value depends on how the method/property is called)
• it is possible that not all the available objects are directly accessible through the API of the instantiated object; in some cases just an object is returned without specifying it's actual type or PID; for this Uniface will then create a handle parameter with an UNKNOWN classification

When using the type library then Uniface:

• will read the library file sequentially and creates signatures for the detected objects, methods, properties, ...
• from here on the process is similar to what /pid is doing
• again, when an unspecified object is returned then Uniface create a handle parameter with  an UNKNOWN classification

The above mentioned tool allows you to check all parameters for the UNKNOWN handle classification and from the search result you can open the affected operations. From there you can easily change the classification.

Besides this the tool also allows you to add a prefix to all signatures or rename them in one go (or individually). You also can rename, copy, or move operations. In addition you also can navigate from one signature to another (by double clicking on the handle classification of a parameter). You can also filter the signatures, import, export, or compile them. There's probably more, but that's all I remember at the moment.

I hope this helps.