Jim Jackson

Hi Vincent, When multiple people access the same project folder, RockWorks has the capability to use different ini files. The ini file hold the plethora of settings used by RockWorks. Since each person might be doing different things in RockWorks that might conflict with other user's settings, you may set a User Prefix to use when Naming Files (Setup Menu | Miscellaneous tab). See the help topic: https://help.rockware.com/rockworks/WebHelp/view_preferences.htm#miscellaneous If you wish to no longer use this feature, clear the prefix value and then in the project's System folder delete all the ini files except Project.ini. Thanks, Jim

Hi Ali, Select the "Other" tab in the Project coordinates system and select the "Set Projection" and then "Select from a list" The datum you are looking for has the EPSG code of 20255 (AGD66 / AMG zone 55). This can be selected when starting a new project or you can Reproject or Reassign from the Coordinates tab. Take a look at the help topic: Custom Coordinate Projections (rockware.com) Jim

Hi Craig, I tried to repeat the problem without success. It sounds like the database just needed refreshed: Borehole Manager | File | Refresh database. What version are you using? Thanks, Jim

There are a few ways to group boreholes. One is to add an optional field, then Filter/Select to update the Enabled flag based on the values in that new field. Another is to create a list of borehole names either by just typing them into a text file or from the Edit menu "Save Enabled/Disabled borehole list", then use "Enabled/Disabled boreholes Based on list" from the same menu to update the Enabled flag when you want to switch. If the boreholes are geographically differentiated you can create a sub-site (which sounds like it would not work for what you need).

RockWorks 17 State Plane is assuming NAD83 not NAD27. You can change your State Plane basis. Under Settings | Coordinates you can Reassign your coordinates: choose the Other coordinates (make sure the radio button is on for Other), then click on the "Set Parameters" drop-down button, and choose "Select from a list". In the search box type "Missi" and you will get a list of the EPSG codes for Mississippi, pick the one that suit you best (Looks like <26795> NAD27 / Mississippi West). Click OK after choosing and then Finish. Now RockWorks will be set for the correct projection and your PLSS Township and Range should plot where you expect them. -Jim

The field StratType._khfacdytr does not exist in your Stratigraphy Types table. In the "Borehole Manager" tab, go to the menu item "File" | "Check Database Integrity". This will sync the Data Dictionary and the database. If you do not want this new user-defined/optional field you can click on the "Stratigraphy" tab, then on "Stratigraphy Types". In the Type Editor dialog select "Edit" | "Edit Fields". Then in that dialog, "Optional Fields for StratType", click on the "_khfacdytr" field, then click on "Delete Field".

An extra note: If you cannot open RockWorks at all due to the "Syntax" Error, delete the ..\RockWorks17 Data\Samples folder. RockWorks will recreate it and recopy the sample files. This is the fall back folder, if RockWorks cannot open your current project, it will try to open Samples, failing that I believe it closes.

Hi Kuldip, I am having a difficulty duplicating the error on my computer. Would you please clear the folder of everything except your Excel file. Then proceed thru your steps again to create the new project. When you get the error dialog, please click on the "Report Error / Restart" button and send the bug report to Tech@rockware.com, to my attention: Jim Jackson. This error report gives a detailed trace of what RockWorks was having a problem with at the time. Thanks, Jim

Hi Kuldip, I am having a difficulty duplicating the error on my computer. Could you tell me more about the folder you are creating the RockWorks project in? It appears to be a network drive, is this true? Was the folder empty when you tried creating the project? Do you have rights to create/modify files in this folder? Can you create a new project on your local hard disk ok? When you get the Error report, please click on the "Report Error / Restart" button and send the bug report to us. This will help me see where the problem is occurring. Thanks, Jim

Hi Kuldip, Could you give me a little more information. Did this occur when starting RockWorks, or during some program function, or just clicking on something? Thanks, Jim

If your RockWorks16 project was initially ok on the local drive, then with RockWorks closed, try deleting the project's "System" sub-folder. When RockWorks opens and you connect to this project, RockWorks will recreate the System sub-folder and the necessary files in it. This process will work for the project on the network drive also. The database needs to have been created correctly for this to work. Then you could give the "Create New Project" another try. I have created projects on my network with out a problem, hopefully this was a just a glitch and will work on a second try. Jim

The limitations of an SQLite database can been seen at www.sqlite.org/limits.html. You should see a performance improvement over using MS Access (mdb) as the SQLite engine is embedded in RockWorks where using MS Access the data had to move (be marshaled) from Access to RockWorks across the COM interface. If you mean MS SQL Server, the limits can been seen at msdn.microsoft.com/en-us/library/ms143432.aspx. With MS SQLServer some of the processing is done on the server but the network latency comes into play. We try to have the server only send back the data for the process at hand, but again large P-Data model will be slow. So I do not have any hard and fast suggestions for limiting the number of boreholes or the amount of data for a borehole, it depends on what you are doing with the data in RockWorks. Once the data is in, you can disable some boreholes.

I went back and looked at this and I believe you can do what you want with the Filter/Select boreholes on the View menu. It does not give you a list it enables/disables boreholes which you can base on a P-Data type.

You could open your project database (mdb file) in Access and run a query like: SELECT DISTINCT Location.Name, PointType.Name FROM PointType INNER JOIN (Location INNER JOIN Point ON Location.BhId = Point.BhId) ON PointType.PointTypeId = Point.PointTypeId ORDER BY Location.Name, PointType.Name; This will give you a list of all the Boreholes with P-Data and the name of the P-DataType

Attached is an example of an RCL file to import P-Data, Jim : Define the input file name, : remember the borehole needs to already exist before the import begins : for Excel the filename variable is XLS_FILE_NAME DEFINE: BM_EXCHANGE ASCII_FILE_NAME C:\Users\Joe User\Documents\RockWorks15 Data\New Project\P-Data Import.txt : This DEFINE is the where the columns in the input are saved : So in this example the first column represents which borehole by Name, : column 2 is the Depth of the sample, : column 3 are Gamma numbers and : column 4 are the Resistivity numbers DEFINE: BM_EXCHANGE ASSAY_FIELDS_MAP Name,Depth,Gamma,Resistivity : Are there column titles in the input file? DEFINE: BM_EXCHANGE INCLUDE_COLUMN_TITLES True : Set the data delimiter if an ASCII file, number 9 is a TAB, 32 is a SPACE, 44 is a COMMA DEFINE: BM_EXCHANGE ASCII_DELIMITER 9 : Run the ASCII import EXECUTE: CSV_2_PDATA : or run the XLS import with the command XLS_2_PDATA : Terminate script without killing RockWorks. EXIT: