![]() ![]() I don’t think the complex relationships (and by that I mean as a video relational database) are fully exploited as of yet. If I were to critique FCPX’s use of data I’d probably use the analogy (danger Will Robinson) in that it is developing a Filemaker underbelly but currently constricted with a Bento like interface. Roles will likely mature as a means of control (my guess of course). The relationship between Events and Projects, is one example as are keyword collections, smart collections, favorites are another. It’s not that other NLEs don’t have some data base functions but that FCPX seems deliberately written to advance on those functions even if not yet fully developed. A lot of the custom info isn’t yet utilized much and a lot of the potential info isn’t yet gathered from the metadata of source files. I see most NLEs other NLEs as more of a spreadsheet.įCPX is still a maturing data base structure. ![]() Sorry.There’s data and there’s data base. I’m afraid I didn’t even keep as detailed notes on the process as I should have, which means it’d take me a lot of time to work through it again.Īnd even if I did all that, now that TapForms 5 is out, with very likely a very different DB schema, I’d have to work through all that before it was useful.Īnd, in case you haven’t already gotten the right impression from all this, explaining it in “simple terms” would prove difficult!Īs much as I’d love to be able to help, I just don’t think that’s practical. I had a Python script that would separate the Bento simple list columns into separate CSV files but everything else (and there was a lot) was manual just because for the volume of data I had that was a lot easier than trying to script it. It exported the data from Bento, imported the main form into TapForms so that I could look at the private TapForms sqlite DB tables to pull out table ID numbers which I’d then edit into the related table CVS files. That would have been really complicated because I needed to do it in several stages. ![]() When I worked out my procedure in the first place I’d considered trying to package it as a “no touch” conversion process. Is it possible for a lot less IT-skilfull person to do, what you did? Would it be possible to ask you for a guide in simple words? I am one of the late migrators from Bento to Tapforms, exactly because i can’t get my simple lists over. It was a messy multi-step process, but it only had to be done once for each of the forms, and then I was blissfully free of Bento. After a lot of experimentation and exchanging information on this forum, I worked out a Python script to massage the Bento export into a form that TapForms could handle. The only problem I had was that I’d used Bento Simple Lists for several critical databases to record multiple values and TapForms can’t import those. It worked great for most of my Bento data. But it’s best to - and for anything complex you need to - export from Bento as a “template”, including all the data, and then use File > Import Bento Template … to import that template into TapForms. You have to Export from Bento and then Import into TapForms.įor very simple isolated forms, you can just export from Bento as a CSV and import that into TapForms. TapForms can’t import a “raw” Bento database file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |