Search the Community

A user in the Czech Republic recently contacted us after installing RockWorks17 on a new computer. On startup RockWorks displayed this error message: No mapping for the Unicode character exists in the target... and the program generated a bug report: exception class : EFDException exception message : [FireDAC][Comp][Clnt]-340. Driver ID is not defined. Set TFDConnection.DriverName or add DriverID to your connection definition. As it turned out, the connection parameters were correctly defined in the project's "menus.ini" file. But the default database file path in the same section contained a strange character. His user name in Windows contained the "š" character which had somehow been incorrectly stored in the INI file, making the file path unreadable. Since his computer was correctly set up to use Czech as the system language, the fix was simply to close RockWorks, rename the \Samples\System\menus.ini file, and restart RockWorks. The settings file was rebuilt, the correct character was stored this time, and the program started successfully. Another note: RockWorks17 and LogPlot8 support Unicode. If you are using LogPlot7 (not Unicode compliant) and have problems entering/displaying certain characters. be sure you have defined your language (such as Czech or Slovenian) as the Language for Non-Unicode Programs in Windows Control Panel | Time and Language | Region and Language | Administrative Language Settings. Molly RockWare Inc

LogPlot8 supports Unicode characters, but older versions did not, and many non-English-language characters were not supported. If you are a Windows10 user, here are some steps you can follow to display specific language characters in programs which are not Unicode-compatible. Open the Windows Control Panel. Click Time and Language. Click Region and Language. Scroll down, below the languages which are displayed, and click Administrative Language Settings. Under the section "Language for non-Unicode programs" be sure it is set to the desired language. Since old versions of LogPlot do not support Unicode (LogPlot8 does) you have to load this "code page". If it is not set to the desired language, click the Change System Locale button, select the language, and click OK. Click Apply and OK. You may need to restart Windows to apply these changes. Thanks to Tomo for bringing this to our attention! Molly Mayfield RockWare Inc

A user recently asked: Just wondering whether you might be able to tell me where im going wrong. I have imported a .las file an constructed some basic logs of the data. I can view these in the Logplot view window. However when I go to export into an EMF format, all the options are greyed out, even jpeg export and other export options. Is there something I have forgot? Our reply to their email bounced, so we'll post it here: The exports are disabled in the LogPlot trial version. You are welcome to contact our support staff (tech at rockware.com) for more details, to send us a sample log, etc. Molly Mayfield RockWare Inc.

A user recently asked: Just wondering whether you might be able to tell me where im going wrong. I have imported a .las file an constructed some basic logs of the data. I can view these in the Logplot view window. However when I go to export into an EMF format, all the options are greyed out, even jpeg export and other export options. Is there something I have forgot? Our reply to their email bounced, so we'll post it here: The exports are disabled in the LogPlot trial version. You are welcome to contact our support staff (tech at rockware.com) for more details, to send us a sample log, etc. Molly Mayfield RockWare Inc.

A LogPlot7 user in Europe started encountering problems after a LogPlot update which also coincided with a Windows update. Each time he tried to access the Compile window in LogPlot, he was the message "Unable to create or display the Depth dialog." We discovered that the Compile window depths and scale, and the log design's Page Setup settings were displaying very, very large numbers, thus mucking up all hopes of meaningful pagination and scaling in LogPlot. Importantly - the Page Setup window showed mixed number formats: the printer settings at the top of the window showed numbers like "123.456.789,00" but LogPlot's page settings at the bottom of the same window (and his Windows 7 system) were using "123'456'789.00" (default for the German / Switzerland setting on his computer). The solution: Access the Control Panel | Clock Language and Region | Region and Language window. Click the Additional Settings button to access the number format options. Click the Reset button at the bottom of the window, to reset all of the number settings back to those which are default for the language-region setting. When LogPlot was re-launched, the Page Setup window showed sensible page dimensions, with the correct number format, and the compiling again worked. Molly Mayfield RockWare Inc.