> For the complete documentation index, see [llms.txt](https://docs.intrepidcs.com/neovi-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intrepidcs.com/neovi-api/win32-api-overview-intrepidcs-api/structures-types-and-defines-overview-intrepidcs-api/setting-structures-overview-intrepidcs-api/using-an-array-instead-of-a-message-structure-intrepidcs-api.md).

# Using an array instead of a message structure - intrepidcs API

In some programming environments (such as [LabVIEW](/neovi-api/basic-operation-intrepidcs-api/using-the-api-in-labview-intrepidcs-api.md)) it maybe inconvenient for you to access the [message with a structure](/neovi-api/win32-api-overview-intrepidcs-api/structures-types-and-defines-overview-intrepidcs-api/setting-structures-overview-intrepidcs-api/message-structures-neovi-api.md). In these cases you may use a byte array in place of the structure. Table 1 below lists the locations of message items in the byte array for a 64 bit version of the structure. The message structure is 8 byte aligned. Padding bytes are marked in black.

**Table 1 - Position of Message Elements in the Byte Array**

![](/files/xdQIADppdEqm9wKZQbEH)