Hello OF Team, I am building a survey to re-sample a plot network where data already exists for thousands of trees. My use case is very similar to this user, and I believe a lookup table is also the best solution for me. I am having trouble determining the workflow for building a lookup table, inserting it into the .collect file, and importing back into Collect. Are you able to provide detailed documentation with step-by-step instructions for implementing lookup tables in Collect (and Collect Mobile)? Thank you! Bryant asked 10 Mar '23, 00:23 bryant |
Dear Bryant,
It's important that the table has a column "id" and this must be the primary key of the table. Please let us know if you need further support from our side, many thanks. answered 10 Mar '23, 07:20 Stefano (OF) ♦♦ |
Thank you for this response! Which option should I select when exporting my survey (prior to building the lookup table) in order to generate the correct type of file? The only .db file that I know how to generate is by exporting my survey to the Collect Mobile format, but this does not seem like the right option for when it comes time to import the survey back into Collect for testing. I understand how to create the structure of the table like you demonstrate with a .sql file and a SQL client, but how do you "fill it with values"? Thanks! answered 17 Mar '23, 22:56 bryant |
Dear Bryant, answered 21 Mar '23, 22:02 Stefano (OF) ♦♦ |
Thank you for the reply! I was initially confused on how to find/generate the "collect.db" file, but realized that this file is automatically created by Collect and stored in the OpenForis\Collect\data. After locating this file, I was able to follow your instructions to edit and fill a new table. It worked beautifully in Collect desktop! Thank you for your help! answered 21 Mar '23, 22:08 bryant |