Right now I only have 3 records in my project, but when I look in the table manager, there are lots of records in every table. Is this normal?
What makes you think you only have 3 records in your "project" if the file contains 11 tables, each of which can hold any number of records?
Any given layout will reflect the number of records which exist in that layout's base-table after you select
Records > Show All
Try saving a clone of your file for comparison. A CLONE will start with all tables empty of records.
Don't have any table named projects so how can you know that you only have 3?
Can't say much more than that from the info provided
Ah I see. I have a wrong idea of what the definition of a record is in that case. I though having for example 3 movies in my database would mean that every table would show 3 records. Still a newby here...
if you think you should only have 3 records and you have a table with 14699 records in it you should probably stop what your doing and learn some FM basics first..
Not a very helpful comment, everybody here learns while doing and making mistakes and hopes to grow with helpful comments of others. Of course I am reading up on FM all the time and only come to this forum when I cannot solve something I am struggling with or have questions about.
Here are the sizes of the exported tables which clears up for me why especially the Plot Points table takes so long to export. Importing goes very fast though and this isn't something I will have to do often.
You may have 3 movies, but you may also have a table of actors and there may be 20 actors in each film, hence 60 actor records, but only 3 movies (for example).
Looking at the number of records you have in the various tables I wonder if you have taken on an existing database or built this from scratch?
I created it from scratch while learning FM. It's not s normal movie database, but it's based on a screenwriting story developing book, so it has a lot of layouts, fields etc. I believe it's pretty much finished now and it works as I hope it would, I was only wondering if it's supposed to have this large database files that are the exported tables, but maybe it's correct because there's a lot of information in this solution.
Just wondering... Why is there such a big difference in size between the exported tables of the solution and the solution on its own? The amount of records inside the program is the same. The solution is 96 mb, but the exported tables have a total size of 709 mb.
To keep the program size down, I am wondering if it's better to use "Save a Copy As..." than to use the export/import option. For my situation, I think that the only downsize to take out the export/import option is that incase I come with a program update in the future, the users cannot import their work in the update but need to enter everything manually again.
I guess when exporting you selected fields from layout (default) not table, so exported files have values from related fields.
(But "The amount of records inside the program is the same" ?)
To make backup, "Save copy as" is better than export each table.
OTOH, it looks a bit odd that many tables have exact same number of records in first screenshot.
If you are exporting tables to separate files, each file contains some "file code" beyond the data. In the single file solution, only one set of file code is required. Often, file structure is larger than data.
Without giving away the name, it looks like a certain "theory of story" that's been kicking around for decades... I considered building a database based on this years ago, gave up and just bought the software.
Would love to see some screenshots or a demo if you're releasing this as a commercial product.
I am in talk with the author at this moment and he's very enthusiastic about the software, he told me that he wants to get it released, no date set yet though.
Retrieving data ...