Use of API in Standard License

Hello, thank you for your reply.

The reason for migrating to API functions is that I need to have dynamic control over the loading and unloading of the DLL, and from what I have found, the use of visual components makes this loading automatic and does not allow manual unloading.

I need to have that control over the DLL because, when processing batches of thousands of labels (even if done in blocks), it seems that the list&Label engine freezes after a few hours, blocking the execution of the software.

I had thought that, instead of using the VCL visual components, if I use the API, after each block of labels I can completely restart the components and the DLL itself, to not overload the engine.

Regarding CMBTLANG_ENGLISH, that is precisely how I was opening it, and it keeps giving me error -101.

I tried the solution in this link:

But I couldn’t find the .PX files mentioned in the link.

That’s why I wondered if this approach was limited in the Standard Edition.