tst
Despite the fact that CINs are not supported by NI technical staff, they continue to work on all LabVIEW 32-bit systems. The VI mentioned above works pretty well on my LabVIEW 2015. So, it's not the case when it just stops working at all.
Generally, CIN is standard DLL with specific export table. It can be easily extracted from original VI by copying lvs*.tmp file from Windows Temp directory when source VI is loaded into memory. Then its extension should be changed to *.dll. That library exports GetLVSBHeader function which returns a pointer to some table with all CIN functions adresses. With some pointer manipulations we can get CINRun function which is called whenever we run any VI with a CIN. It should be done in separate wrapper library, of course. I may illustrate such approach, using the CIN in Prompt and Save UDL.vi (please, see the attachment).
JLuna
If CIN loses its resource code in LabVIEW x32, it says that loading of the DLL fails for any reason. It's very often an absence of dependent libraries which final CIN library was compiled with. In your case it's likely that there's a problem with ole32.dll. It may be not found or corrupted or has mismatching version. Please, try this "CIN to DLL" wrapper method. If it works for you, then you might turn it to a sub VI and modify Prompt and Save UDL.vi with it.
