RE: Win32API setup woes
I am happy to report that with the help of the NUG, I was able to debug so that I now have this fixed. It was due to an error in the way I had the various directories laid out. Took me a while, but I was able to get everything aligned correctly with the insights from this group. Thank you David -Original Message- From: David Garrard [mailto:dgarr...@gmail.com] Sent: August 23, 2019 7:21 PM To: '4D iNug Technical' <4d_tech@lists.4d.com> Subject: RE: Win32API setup woes Hello Keisuke and Timothy, I have isolated things to a simple new structure "TestDB.4db" that has one method that calls a couple Win32API commands. I downloaded the latest Win32API for Github and have placed it in the \Plugins directory next to this structure. There is no \Win4DX directory for this test setup. On one Windows computer this structure shows up correctly in the 4D Explorer and is enabled - version 8.2.2. When I execute code with the Win32API commands on this computer all is good. On the other Windows computer this structure shows up in the 4D Explorer, but is marked as Disabled - need to upgrade. Both these computers have Microsoft Visual C++ redistributables installed. X86 and 64bit. Both are using v16.3 Build 16.217894 32 bit. One thing that might be associated is that when I compile the compiled structure is placed in a directory entitled "STR# 10135,18", instead of "Compiled Structure". I had ignored this since I am seeing the Disabled state of the plugin in the interpreted database, but perhaps there is some string resource issue that might be causing this problem. So if anyone knows how to fix that issue, it may address the disabled plugin issue. Thank you, David -Original Message- From: Keisuke Miyako [mailto:keisuke.miy...@4d.com] Sent: August 21, 2019 7:58 AM To: dgarr...@gmail.com; 4D iNug Technical <4d_tech@lists.4d.com> Subject: Re: Win32API setup woes license error is the default exception when a plugin call fails. the real cause could be anything. first you should check in 4D's explorer that the plugin is loaded. if not, you'd get the licensing error. maybe you are missing vc runtimes. maybe the architecture doesn't match. keep in mind that 4dx folders are not supported in 64bit since v12, and all platforms sine v14. 株式会社フォーディー・ジャパン 宮古 啓介 テクニカルサービスマネージャー 〒150-0043 東京都 渋谷区道玄坂1-10-2-6F Phone : 03-4400-1789 Fax : 03-6427-8449 Email : keisuke.miy...@4d.com Web : jp.4d.com ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: Win32API setup woes
What drive are you putting the result. I have found problems when on c Regards Chuck Sent from my iPhone > On Aug 23, 2019, at 7:20 AM, David Garrard via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hello Keisuke and Timothy, > > I have isolated things to a simple new structure "TestDB.4db" that has one > method that calls a couple Win32API commands. > > I downloaded the latest Win32API for Github and have placed it in the > \Plugins directory next to this structure. There is no \Win4DX directory for > this test setup. > > On one Windows computer this structure shows up correctly in the 4D Explorer > and is enabled - version 8.2.2. When I execute code with the Win32API > commands on this computer all is good. > > On the other Windows computer this structure shows up in the 4D Explorer, but > is marked as Disabled - need to upgrade. > > Both these computers have Microsoft Visual C++ redistributables installed. > X86 and 64bit. > > Both are using v16.3 Build 16.217894 32 bit. > > One thing that might be associated is that when I compile the compiled > structure is placed in a directory entitled "STR# 10135,18", instead of > "Compiled Structure". I had ignored this since I am seeing the Disabled > state of the plugin in the interpreted database, but perhaps there is some > string resource issue that might be causing this problem. So if anyone knows > how to fix that issue, it may address the disabled plugin issue. > > Thank you, > > David > > -Original Message- > From: Keisuke Miyako [mailto:keisuke.miy...@4d.com] > Sent: August 21, 2019 7:58 AM > To: dgarr...@gmail.com; 4D iNug Technical <4d_tech@lists.4d.com> > Subject: Re: Win32API setup woes > > license error is the default exception when a plugin call fails. the real > cause could be anything. > > first you should check in 4D's explorer that the plugin is loaded. if not, > you'd get the licensing error. > > maybe you are missing vc runtimes. maybe the architecture doesn't match. keep > in mind that 4dx folders are not supported in 64bit since v12, and all > platforms sine v14. > > > > > 株式会社フォーディー・ジャパン > 宮古 啓介 > テクニカルサービスマネージャー > 〒150-0043 東京都 渋谷区道玄坂1-10-2-6F > > Phone : 03-4400-1789 > Fax : 03-6427-8449 > Email : keisuke.miy...@4d.com > Web : jp.4d.com > > > > > ** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ** ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
RE: Win32API setup woes
Hello Keisuke and Timothy, I have isolated things to a simple new structure "TestDB.4db" that has one method that calls a couple Win32API commands. I downloaded the latest Win32API for Github and have placed it in the \Plugins directory next to this structure. There is no \Win4DX directory for this test setup. On one Windows computer this structure shows up correctly in the 4D Explorer and is enabled - version 8.2.2. When I execute code with the Win32API commands on this computer all is good. On the other Windows computer this structure shows up in the 4D Explorer, but is marked as Disabled - need to upgrade. Both these computers have Microsoft Visual C++ redistributables installed. X86 and 64bit. Both are using v16.3 Build 16.217894 32 bit. One thing that might be associated is that when I compile the compiled structure is placed in a directory entitled "STR# 10135,18", instead of "Compiled Structure". I had ignored this since I am seeing the Disabled state of the plugin in the interpreted database, but perhaps there is some string resource issue that might be causing this problem. So if anyone knows how to fix that issue, it may address the disabled plugin issue. Thank you, David -Original Message- From: Keisuke Miyako [mailto:keisuke.miy...@4d.com] Sent: August 21, 2019 7:58 AM To: dgarr...@gmail.com; 4D iNug Technical <4d_tech@lists.4d.com> Subject: Re: Win32API setup woes license error is the default exception when a plugin call fails. the real cause could be anything. first you should check in 4D's explorer that the plugin is loaded. if not, you'd get the licensing error. maybe you are missing vc runtimes. maybe the architecture doesn't match. keep in mind that 4dx folders are not supported in 64bit since v12, and all platforms sine v14. 株式会社フォーディー・ジャパン 宮古 啓介 テクニカルサービスマネージャー 〒150-0043 東京都 渋谷区道玄坂1-10-2-6F Phone : 03-4400-1789 Fax : 03-6427-8449 Email : keisuke.miy...@4d.com Web : jp.4d.com ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
RE: Win32API setup woes
Quote: > first you should check in 4D's explorer that the plugin is loaded. if not, > you'd get the licensing error. See also: https://kb.4d.com/assetid=77737 https://kb.4d.com/assetid=76951 -Tim ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: Win32API setup woes
Hey David, Why are you using a Win4DX folder and not just putting the bundle into the Plugins folder? I’d start there. > 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 ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: Win32API setup woes
license error is the default exception when a plugin call fails. the real cause could be anything. first you should check in 4D's explorer that the plugin is loaded. if not, you'd get the licensing error. maybe you are missing vc runtimes. maybe the architecture doesn't match. keep in mind that 4dx folders are not supported in 64bit since v12, and all platforms sine v14. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
