Good to hear

Sorry Trent, I just overlooked the Common Files part of your location description. Yes, the package is there.

Jerry J. Jansen

No.  There is not any difference between the trial and full version other than your license and you get the source code with the full version.  Are you running a 64-bit OS?  If so, then it will be the Program Files (x86) folder instead.  It has to be there otherwise you would have received a different error when you tried to import the table structures within the DDT.  So the file is out there somewhere, and it has to be in the Common Files\MicroFOur\StrataFrame folder.

Let me know what you find...I am curious now

Checked all subdirectories and no *.pkg files. Could it be because I am using the trial version?

Jerry J. Jansen

Hmmmm....you should have a file with the same name in the following location....assumming your Common Files folder is the default location:

C:\Program Files\Common Files\MicroFour\StrataFrame

You should be overwriting the file that is there.

Thanks Trent, there was not one there so thought it had to be opened. Sorry.

Jerry J. Jansen

Just right-click it and save to the above specified location.  You do not need to open the PKG file itself, just copy it to the Program Files\Common Files\MicroFour\StrataFrame folder.  The password is "framework" but there is no need for you to get into this package file directly.  This will just resolve the issue the next time you click "Add Localization and Messaging Tables"

Thanks Trent but the zip file is asking for a PASSWORD.



Just started to try out StrataFrame so thanks for the info about embedded files. I will take a look at the documentation.

Jerry J. Jansen

Here is the updated package file.  Just copy it to Program Files\Common Files\MicroFour\StrataFrame.  The reason other developers have not run into it is because most people embed their localization files, which is the fastest and recommended way if you are looking for the fastest message and localization solution.  It also makes distribution easier.  This is the same approach that we use...and why we did not catch it .  You can learn more about the different ways to distribute your localization files in the help docs, but our recommended way is by using the embedded approach.

Hrm... looks like the .pkg file needs to be updated to include the names of the stored procedures.  Strange that no one has run into that problem before.  Thanks Jerry