#Baseelements export filepath pro#
#Baseelements export filepath mac#

#Baseelements export filepath pro#

I’ve posted a bug report as I think it’s a general error with not only the DDR but also the copy paste mechanism in FileMaker. BaseElements is a tool to assist FileMaker Pro developers, and make development easier and efficient. Things like high ascii or other characters that should be encoded in XML and aren’t being properly encoded. I’ve found that the DDR in 11 includes characters that the v10 DDR would strip out of your files. The second issue is more of a workaround. We’re working on that so will have an answer for it soon. There are two outstanding issues to resolve before I can turn this over from beta to final : First, there is a plugin issue that causes an out of memory error on large solutions. The best way to convert paths is to use the native FileMaker functions ConvertFromFileMakerPath and ConvertToFileMakerPath. They haven’t propagated all the way through yet to the other layouts, but hopefully I’ll have more on that tomorrow. Also you may notice ( or not ) the new logo on the about screens. Mostly this fixes issues with CF references introduced in 8, but also some display oddities and a few other bits and pieces.

Added back preview mode to the view as Custom Menu so you can actually get out of preview mode. The feature to export the cube is described in the evaluation guide.

#Baseelements export filepath mac#

I've developed a Filemaker 10 database on the Mac platform that I now need to port to Windows.

Changed the CF missing warning from ValueList missing to say CF missing. Subject: Re: BaseElements-Plugin BEListFilesInFolder ( path ) On, at 11:42 AM, MHardee wrote: I've just installed this plugin and am trying it out and have a couple of questions (if permitted).

If you're having a plugin related issue with one of our products such as the BaseElements developer tool, there is a specific product related support site for BaseElements : ().

Fixed an issue where there were false CF missing warnings. For technical issues related to the programming or building of the plugin code, use the GitHub issues pages.