Hello,
I have 2 separate systems that came from the same code base that use WIN32API. Both are Windows and version 16.3 of 4D single user. Both have the WIN32API.4dx and WIN32API.rsr installed in the \Win4DX directory found in the same directory as the .4DB I do not have a Win32API.bundle in the \Plugins directory on either instance. When I run them interpreted, one of the databases reports a "Incompatible version. You need to upgrade your plugin. Licence or privilege error. (Win32API)" in my startup method when I call sys_GetUTCOffset. (Because of the word "privilege" in the error message, I have checked the read/write state of the WIN32API.4dx and WIN32API.rsr on both instances. Neither is read-only.) From what I can tell they are the same vintage WIN32API. In fact, I have replaced copies of the "bad" WIN32API.4dx and WIN32API.rsr files with the functioning WIN32API.4dx and WIN32API.rsr files. They are the same file sizes. Still fails. I have also done the following with the failing instance: - Removed the WIN32API.4dx and WIN32API.rsr from the \WIN4DX directory in the same directory as the .4DB - Added a version 8.2.2 instance of Win32API via a Win32API.bundle in a \Plugins directory in the same directory as the .4DB - Started up with the slightly different failure: "Incompatible version. You need to upgrade your plugin. Licence or privilege error. (Win32API(8.2.2))" The other instance of where I use the same code on a slightly different 4D application and same \Win4DX directory setups works fine - executing calls to several different Win32API sys commands such as sys_KillProcessID, sys_isAppLoaded and sys_GetUTCOffset. Can someone provide some direction? Perhaps you have a functioning setup on v16.3 that uses WIN32API and you could share the placements. Or a trick that I am missing. Thank you, David ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
