John:

A couple things come to mind. The version of Foundation that I’m using with
V17 is 5.7. I think 5.6 will work with the exception with how images
display in the toolbar. Walt will be the best source of info on that.

I have hit issues with components when they’re compiled only for 32-bit.

It could be a long shot but open the source code version of Foundation,
compile for both 32 and 64-bit, and then build the component. That could do
the trick but, as I see it, that’s solving symptoms. The underlying issue
is getting the right version of Foundation and I think 5.7 is the one that
you need.

[back to lurk mode so I can carry on with my house-moving chores]

--
Douglas von Roeder
949-336-2902


On Mon, May 20, 2019 at 2:57 PM JOHN BAUGHMAN via 4D_Tech <
[email protected]> wrote:

> I am trying to upgrade a v13 database to v17 and am taking it first to
> v14. I am working on a Mac but it is deployed on Windows 10. I have it
> upgraded on the Mac with everything working including the PKUID fields.
>
> I plan to test each upgrade step in Windows. After moving the v14 upgrade
> over to my  Windows 10 VM I get the following error when opening the
> database with 4D Server v14.6 (64bit)…
>
>         Error Can't load component "Foundation_560.4DC”.
>         Error code: -10510 Can't load component "Foundation_560.4DC".
> component: '4DRT' task -3, name: 'Client Manager’
>          Error code: 6 Could not find compiled runtime information while
> loading database or component "Foundation_560". component: '4dcm' task -3,
> name: 'Client Manager'
>
> It works fine with the interpreted version of Foundation. I tried building
> the compiled version in windows and still get the error.
>
> I can deploy interpreted, but wondering if why I am getting the error
> compiled.
>
> Thanks
>
> John
>
>
>
> John Baughman
> Kailua, Hawaii
> (808) 262-0328
> [email protected]
>
> **********************************************************************
> 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]
> **********************************************************************
**********************************************************************
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]
**********************************************************************

Reply via email to