I am trying to generate a product stock report in PDF. To do this, I first created the report in HTML.
Firstly I created the table with the list of products and at the end of this, a small table with the taxable base, the VAT and the total of selected products.
The problem is, that table is divided if there are too many lines in the list. For example, you can leave the tax base and the VAT on the first page and since the total does not fit anymore, you can move it to the next one.
What I need is that this small table should be inseparable and that if it does not fit in one page because the list is very long,it should jump to the next one.
I tried using page-break-before property but it does not work at all.
Any recommendations on how I can do it?
Thank you!
You can try to put <div> ... </div> as a page break.
If not in the css file : the div : display: block
I have a sales table, witht he number of sales and the value for each store, grouped by the hour.
What I would like to do, ideally without the use of a subreport, is add a pie chart that details the number of sales by store for each hour and embed this into the table. The intention is to hide the store-level breakdown and toggle display on SaleTime. The pie would become visible for each drill-down row.
Screener to show what I mean
The pie needs to exist within the table for each saletime, something like the below mockup:
Any thoughts?
I have a purchase order form in SSRS. It's grouped on the Purchase Order number. There are four rows in the group footer for totals.
Is there a way to keep all rows in the footer together? That is, if all of them won't fit on the page, that all of them will be printed on the next page.
You have two ways of attempting to accomplish this. Using the KeepTogether property for the selected rows or the entire group
Or when SSRS inevitably doesn't do what you want it to do, you can do the ole Rectangle and Textbox trick. Insert a row above the subtotal that is also a group footer. Then insert a rectangle. Once you do this, you can insert a bunch of text boxes and move them freely around and structure them in the same way you had them formatted the 4 separate rows. It would look something like the below. With this way SSRS couldn't split the row onto multiple pages because its all in the same row. For insurance purposes check the KeepTogether box for this row as well.
Basically, I'm trying to make a database of collectible cards as a project to get familiar with MySQL and I'm unsure about how to approach setting this up.
Essentially, the database boils down to holding information about individual cards. For example a card will have:
A Name
Some text associated with the card
Color
Also, these cards will belong to sets. A set is a group of cards released in that set. The only information stored about a set is:
The name of the set
The release date of the set
I was approaching this as a many-to-many relationship joined in a joiner table. Since one card can be in several sets and one set can contain multiple cards it made sense.
However, I have a couple problems with this setup.
The first is that information about the card can change with each set, but it is still the same card. For example, the text associated with the card may change but the card is still the same. Instead of having a new card for each set it is in, how would I go about reusing the information that will stay the same and only reflecting the change in text depending on the set? I was thinking about having another table of just card texts which would be linked in the same joiner table. Is this setup possible, and if it is, is it recommended?
Another problem I'm having trouble with is the issue of color. Every card will have a color, but the amount of colors a card may have can vary. For example, a card may be gold, white, and orange and another card may just be green. I would like for this database to allow searches for cards based on their color and for it to output a list of all cards of a color or combinations of color.
To do this, I was thinking that I would have a separate table for each color and implement this as a one-to-many relationship between the cards and colors. Does this make sense?
Thanks in advance and sorry if I sound like an idiot.
It sounds like you're on the right track, but I don't like the idea of creating a separate table for each color. Instead, I recommend doing something like this:
Create a Card table with all of the information that stays the same about the card. Each row should have a unique card ID.
Create a Set table that contains information about the set. Each row should have a unique set ID.
Create a Color table that has a row for each color with each color having a unique color ID.
Create a CardText table that contains the text, the card ID, and the set ID.
Create a CardColor table where each row has a color ID, card ID and set ID.
I am developing stock inventory for Bicycles.
I stored Cycles cid,title, desc etc, in CYCLE table, and another STOCK(sid,cid,qty) for storing stock.
Now i cam to know that Bicycles can have many colors(Black, Red, Orange etc.) AND sizes.
I am confused about storing Stock with respect to Size and Color.
I Modified the STOCK Table
STOCK(sid,cid,qty,color,size).
e.g.
1,101,12,1,null for Red Color
1,101,12,2,null for Green Color
...... (6 records for same cycle with respect to color as there can be 6 colors)
PLUS
Size medium,Large,Small (3 records for same cycle with respect to size)
1,101,12,null,medium - for Medium size
1,101,12,null,Small - for Small size
1,101,12,null,Large - for Large size
Total 9 records for 1 Cycle product.
I have another design in mind for stock
STOCK(sid,cid,qty,red,green,blue,orange,cyan,yellow,medium,Large,Small)
and 1 single record in stock.
1,101,0,0,1,3,5,6,3,0,7
My question is,
Is this right way to maintain a stock, or i can improve.
If you can help to fine tune, i will greatly appreciate.
Your design should be like this:
Cycle table: only 'properties' of the cycle
CID, COLOR, SIZE, PRICE etc
You'll set your size to "SMALL", "MEDIUM" etc
You'll set your color to "RED", "GREEN" etc
Stock table: only maintain the quantity & related details
ID, CID, QTY, DATE_OF_ARRIVAL_OF_SHIPMENT etc
So now, each row in the Cycle table identifies a 'type' of cycle, and each row in the stock table identifies some cycles in stock.
This is good because now, if you have to add another color / size, you only need to create another row in your table, not modify your structure. Also, now you can write simple queries for all your characteristics (e.g. how many cycles of red color across all sizes are in stock?)
Hope this helps!