One more clarification: This seems to happen only with 4D standalone/remote - not with 4D Server (either 32 or 64 bit). That is, I can run server on the VDI and it will properly execute A4D and OT commands. However, if I connect with 4D remote, I cannot run any A4D commands. Same issue if the structure is run directly in standalone mode.
So, the issue doesn't *seem* to be with the .dll files themselves, as they are properly used by 4D Server. However, some combination of the 4D standalone application, a legacy structure file and the VDI environment seems to be at play. The error message we receive is the same message one gets if the .dll files are physically removed from the plugins folder. - Clayton _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
