Learning hyperreport

Yes this is all true, but if you haven't started using hyper reports alot yet, seriously think about what your getting into.
We use them for 99% of our programs, they are wonderful to have, as someone put it, for the supervisors and operators to easily read, and you can customise them anyway you want......But, and there is always a but....
the hyper reporting fuction can be a pain in the behind, as we have found out since switching to 3.7. We have a brand spanking new computer, multiple processors etc., and still we crashed on a regular basis--by this I mean several times in one day.
We found that since our hyper reports/programs were all on our server (to assure the higher-ups that everything is backed up each day, and they want all info on the server), we had communication problems.
We eventually had to move all the programs/reports to the local computer, and we still crash about 2 times a week. (much less is we re-boot the computer at least once a day)

I suspect that we are not the only ones who were/are having these problems, otherwise why would B&S decide to get rid of the hyper reporting function?!?

Are you under sma, what version are you on now, and will you remain on that version for awhile?
If you go to using hyper reports, and then switch to 4.1, you will be SOL to create new reports.

From what I understand, there is an inspection report function within the new versions that will be similar but more user friendly.

I will be awaiting that myself, but as 4.0 is gone with the wind, and I will not go to 4.1 until is has been tested by many folks here and reported on (positively), so it may be some time before we switch over.

Just an idea, but I found a few years back that I was having issues similar with the crashes, and I started using powerpoint slideshows instead and the problem seemed to go away.

I can't be positive as I was never able to gather any supporting evidence to back this, but, my belief is that because hyper report depends on .bmp for photos, which are huge, plus the need to not only store the hyper report which many times contain active x objects plus the original .bmp that this is a whole lot to deal with for a local drive, unless the drive they are kept on is a secondary drive independent of the OS, strictly for storage. But as I said, the powerpoint slideshows have worked for me for quite awhile and they are much easier to incorporate into the program through ext objects menu and they are alot smaller in size. But, if powerpoint isn't an option, I would say get a 80 gb hard drive or larger, install it as a slave and keep it strictly for local storage. This is the same situation I warn ppl of when it comes to storing mp3 or any live media format on their pc. Best bet is to keep that stuff away from the OS, and just maybe the crashes might stop.

Just my .02

"supervisors" in our shop, generally speaking they are one step up the ladder from the amoeba.

Ouch! (Former VB Programmer 7yrs! )

Originally Posted by jon_dav_uk
"supervisors" in our shop, generally speaking they are one step up the ladder from the amoeba

Maybe I was being a bit harsh with the above statement.....I apologise wholeheartedly to all the amoeba out there

NOOO PROBLEMO! I know where you're coming from!!

Shelly, cool to see you how have things been treating you? I too blame the .bmp thing. I am not sure why they never supported .jpg. I love Hypereports for pre inspect set up instructions and operator input. If you find the message boxes offered by PCDMIS too limited Hypereporting offers a lot in regards to operator input. I agree with Andrew though that they suck for post inspect reporting. If you want help on some pre inspect stuff PM me I use them a lot for that (like Shelly 99.9% of my programs). If you want to use it to report dimensions then I think you may be better off going another route.

Craig