If I can be of help, I'm working on an ERP.
I have some love-hate feelings with AppGini in this venture. In one hand, I choosed AppGini because flexibility, I can focus on my business logic, and Table VIews and detail views are automatically generated. On the other hand, we are coding a lot of custom code for this autogenerated screens fits our needs. Don't take me wrong, this is not bad at all, In other situations I'd have to develop it anyway.
Because my obsession to not modify appgini generated files we are coding from hooks.
I though in some schema similar to yours, but is not a good idea for several reasons. Once, as you say, related tables. You have to think too about permissions, menu and so on. Because AppGini menu is very basic, I'm developing my own menu library and my own permissions system.
I miss views and custom fields too, there are in roadmap, but not ETA, And alternative to lookups to choose from a datatable (for example, an input with a button, and when pressed, opens a popup with a tableview to choose one record and return a value). This probably I have to developit from zero.
Sadly, new versions with improvements don't release very often
Obviously AppGini was not created for complex projects. This don't means is not possible, of course you can, but is not a path of roses if you are not an experienced developer, because you have to support it with several third-party libs to fit where AppGini fails
Then here we go. Sometimes I hate AppGini because lack of very basic features. Other times, I love it because you can extend it very easily.
Sorry, I forgot the main question ROFL.
- Right now, work with different projects is not worth.
- In the time of this writing, my project file has 109 tables and growing and I don't remember the number of fields. Project size is right now 3MB
Professional Outsourcing Services