This is probably bad practice but it does work, and for large UDT’s of mixed data types it seems to be faster than padding and de-padding. If I “PUT” a UDT to a file (on a ramdrive) from VB then “GET” it from PB/DLL there is no need to pad or de-pad it as must be done if the UDT is passed fromVB. I’d never write a new App. doing this, but this works great for older 16 bit VB
apps. that are ported to 32 and need the power of PB/DLL.