What you describe can certainly be done, though the starter solutions may or may not be the best starting point for you here. The key question, though, is are you prepared to invest the time needed to learn how FileMaker works and how relational databases are designed?
You've described a pretty ambitious project here for a beginner to take on. To do this, you'll need to spend some time with on line tutorials and/or reading a book or two on Filemaker and Database design. We'll be glad to help, but drawing on those resources will help you get up to speed much more quickly than trying to accomplish this all through a forum. The fact that you want to publish the database to the web adds an additional level of design requirements to your system as you'll need to design interfaces that work within the limitations of Instant Web Publishing.
You might want to consider hiring a consultant to set this up for you instead.
If you do want to created this all your self, I suggest tackling this in stages. First, you'll need a sound data model that identifies all the tables and relationships you'll need in place to make this work. Then you can compare this "paper design" to the starter solutions' data models to see if any of them can be adapted to serve as part of your system. From there you can set up layouts/scripts for Inventory control and others for placing and filling orders--with inventory levels updating with each order.
Thank you for your response. I have written everything I can think of on paper and put most of it in the database I created. Is there a simple layout/script for my inventory control. Formula....perhaps. Can you direct me to where I can get help that I can get online free as I am sure I will not get funding for tutorials. And absolutely; they will not pay for someone else to create the system. So I am stuck to figure this out on my own.
any help I would appreciate just to get me started and I will try to find a good book and learn more in time.
That depends on your table structure, which you haven't shared in this thread. You might upload a screen shot of Manage | Database | Relationships to your first post in this thread (click the edit link).
Typical invoicing system starts with this basic table structure:
Invoices----<LineItems>----Products (books in your case)
You can use fields in Products to compute current inventory levels and also identify products that have reached their re-order points. The LineItems table can be used to log all changes to the inventory. You can log not just items sold, but also shrinkage and the reception of new shipments in this table by adding another layout for recording those inventory changes.
Note, the rudimentary inventory control in the Invoices starter solution has some significant design flaws that make it possible for user errors to introduce errors in your inventory counts.
So the first question, is do you have this table structure?
There are training videos about FileMaker on YouTube you might check out.
From what you have just posted I am intrigued. I find this fasinating never the less I have a long way before I will fully understand it I am sure. I have posted my screen shot and doubt I am close to what I need but it is a start. I did say in my first post I have entered all that I needed inclu. inventory - the purchase order information but I have no script and as I see now table structure.
Yes, but the issue is the structure of your database. What tables you have defined and how they are related. I was suggesting a screen shot of Manage | Database | Relationships, not Manage | Database | Fields.
If this is the Invoices starter solution, then you do indeed have this table structure. However, the way this starter solution updates inventory levels is not how I recommend managing inventory. It relies on scripts that can easily be used to remove an item from inventory once or not at all. I'm suggesting a different approach that does not rely on a script at all.
Getting a basic understanding of How FileMaker works and how Relational databases should be designed is a crucial first step here for a project of this scope.
I have not used a starter solution. This is my own. I think I get what you are saying for me to use the relationships to connect them together instead of using scripts. I will be spending my weekend reading how filemaker pro works
Feel free to keep posting back with questions. I've been trying to establish a starting point from which I can help you get a working inventory.
Here's a demo file for Invoices that a person named "Comment" created a while back. It's a very simple, no frills example of how to do invoices. It would make a good starting point for adding in an inventory management capability.