Hi,

Im new to filemaker, and I have a problem with the size of the description on the line items. Basically, after I enter the data, then I click the print mode, I want all of the contents of the product item displayed.

For example, this is what I have at the moment.

- But on the first item there are more details that need to be displayed

like this but I want the list to move down when more content are added so all of the description is shown.

Sorry Im just beginner I hope I could explain myself.

Thanks

Design the invoice print from the line items table and use "sliding" to decrease the size of the body part. Hopefully, you are using two tables: Invoice and InvoiceLineItems, and not repeating fields. Many posts on the forums about this. Search for invoice.

Sorry it still doesnt work and I dont understand fully why.

I resized the fields and made them using sliding up based on all objects above but nothing is sliding up?

Is it sliding up in Print Preview?

no unfortunately it isnt sliding in preview either

Hi ndep2000, Welcome to FM Forums!

Here are basics in case you wish to walk through it again yourself:

1. Select your Item description field and make it very large - larger than the largest item description you may have.
   
2. Select everything inside that body part (lines, text labels, everything) and set them in Inspector > Position > Sliding
   
3. Decide whether objects should slide up only based upon item above or all items. In this instance, since the other items are single line, you can select 'only objects directly above'
   
4. Right below that, also check 'also resize enclosing part (which should really say 'also REDUCE enclosing part' since 'resize' implies it will reduce OR expand and that is incorrect.
   
5. Go to Preview Mode (sort your records first if you have a leading part)
   

If that still doesn't work, can you create an empty clone of your file, zip it and attach it here? We can take a look for you.

Ok sorry I Stilll! couldnt get it to work,-

ıt should be under (teklif) Estimates L74-Print detail

Thank you

ndep2000.fp7.zip

Everything that must slide up must be completely within the body. You have the top of the grey rectangle at 268 but your header ends at 270. It must be completely within the body. :^)

I tried it but it still doesnt slide , I dont udnerstand what Im missing ?

I need you to provide the file again - the one you just fixed - and include several records, then tell me which script you are firing to run it. We'll figure it out yet!

To be honest, I don't know why this file was set up to print from the Estimates table instead of Estimate Lines.

Sorry this is a readymade template which Im trying to make certain fixes on . I dont understand what you mean by scripts ? I have reattached the new file

ndep2000.fp7.zip

Do not click 'print estimate' because it lock you up and trash your file. It asks if you want to print Modern or Basic (but both buttons are broken) and it does not provide the User a way out - no cancel. Lesson reinforced ... always provide a Cancel button. It just trashed another important file I was working in. Bummer.

I do not know what to tell you ... I would not use this file at all. This style of design gives me a headache. I would create the estimate and/or invoice in LineItems table where it belongs. Here is an example of how it should be set up:

http://fmforums.com/forum/topic/63425-auto-fill-one-field-with-text-from-two-fields/page__p__300150#entry300150 :)

the problem is I wasnt using the print estimate button but anyway, I always go back to the same post but I dont understand its all gibberish to me.

Edit- I dont have the knowledge to set up a work like this from nothing, its just a small problem that I need to fix for me to finish working on it

Then I would suggest two possible lines of attack: 1) stop designing and set aside time to learn some basics first or 2) hire a Developer. If the invoices demo is gibberish then there is little we can do to move you forward because it shows the pure essence of relational structure.

FileMaker is easier to design with than Access or other solutions but it still has a learning curve.