Jump to content
Salesforce and other SMB Solutions are coming soon. ×

ha,a puny database.


forbade
 Share

Recommended Posts

This is a really small Database I made in my playground file ( its what I use to trouble shoot Ideas, before I implement them into the working database)

 

I wanted to get your guys opinions on my newb efforts. lol

 

The main thing I wanted to troubleshoot was to be able to add data to a repeating field in a Purchase Order layout. It seems to work fine, but if you guys have any tips or pointers... Im all ears.

 

 

The reason I have the calculation(s) in a separate table is because in the real database, I don't want caculations run every time I access the record to cut down on processor speed. It was kinda pointless for this Database because it was so small. But my thinking behind putting it into a seperate table is to only have a calculation run when specific process's are accessed.

 

Other than that I would like some feedback on the Float table. I was quite pleased with how it turned out. It was the simplest method that came to mind to share data quickly between tables with out having to create a bajillion relationships.

 

I've been in Filemaker 4 months.. and loving it.

Link to comment
Share on other sites

I like the color scheme okay, but the structure needs a lot of work.

 

I strongly recommend going to a relational structure for the line items rather than the repeating fields you currently have. A portal of line items greatly improves the flexibility of the solution by allowing you to easily extend the number of line items and to easily count and view the Invoices where each Product has been used.

 

I would also recommend using table names that reflect the data that they contain. Using generic names is confusing to follow.

 

I'm afraid I don't understand your argument about moving the calc to a different table to improve performance. A stored calc is best if you're concerned about performance, but those cannot rely on data from other tables. Unstored calcs are performed on the fly as needed. Their performance is more a function of their complexity and dependancy on other unstored calcs and related fields.

 

I think you'll have to give some explaination of the 'float' table, as this is not obvious to me.

Link to comment
Share on other sites

This thread is quite old. Please start a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share



×
×
  • Create New...

Important Information

Terms of Use