REP-1814 - Report cannot be formatted

Another nasty error.

This one is hard to workaround particularly when you have complex report structure like several repeating parent child frames and anchoring objects.

If you are lucky then simplest form of error might just mean that the object pointed out in error is going out of page boundary.

If this does not help in resolving then analyze for following possible causes.
1.Find the anchoring objects which are forced to print on the same page but due to size constraints are not allowed to. Try removing the page protect and set the frame object properties to variable and see if error is resolved.

2.Try deleting the object . if the error now moves to another field then it may the case of inconsistent repeating frames. Set all frames "Print object on" to first page and "Base printing on" to enclosing object.

If even that does not help start over :-))
Just kiddin...

REP - 1213 frequency below its group

Allright folks thumbs up here comes our first KED entry for newbies.

REP - 1213 frequency below its group

Now this can be very annoying error to newbies. You can not just put the fields in repeating frames where they don't belong to.
If you have created 2 or more groups in a query and try to put field of say group1 , in a repeating frame of  group2 which lets assume is top level group. You invited this error.

Here lets take an example.

Refer a figure you want your employee table report grouped by department_id and manager_id.

But you only take department id in the upper group and manger id is still in lower group.

While you are creating a parent frame with these 2 fields , you get an error we are talking about just before you run the form

Remedy is simple you have to pull the manager id in upper group. Now real life scenarios wont be that easy. But basics and facts are the only things we should stick to.

Hope I am not confusing though.

The First Post.

Hi Everyone.
I was just thinking whether we should make our blog public or not , may be it is good to maintain a vicinity of our own.
But oh lot of our reusable asset and like projects go fail just because people have to create and maintain accounts and passwords for every darn innovative idea they come with.

Please don't mention the corporate logos and enterprise names here. Lets keep it simple we read and post only technical stuff.

So I made the blog public and also made sure that anybody can comment on the blog.

Hope it serves as a good visiting point then. Happy blogging.