Why would a Windows app do this?

[sactoking]

Ok, where I work we have licensed a small database/interface program to log our output (insurance bonds). We sue dual monitors and everyone would like to be able to open the database on the secondary monitor. Unfortunately, the program crashes when you move it from the primary monitor. The office manager (who's not technically inclined) even went so far as to say that our IT guy (independent contractor) told her that one employee fried their screen by trying to change the database to output on the secondary monitor. I call BS on that story.

My questions are:
Is that answer (the program fried the screen) BS or plausible?
Why would the database not be movable to the secondary monitor? My guess is sloppy programming. There's other evidence of sloppy programming, like some screens supporting 1280*1024 and others crashing due to an unsupported resolution.

The database, I believe, is a shell built on top of MS Access, if that matters at all.

 

[Ken g6]

I'm not sure about the crashing, but the fried monitor has to be a coincidence, like the next-to-last story here.

 

[EagleKeeper]

The display front end may be trying to position itself to a given coordinate. When the coordinates of the second monitor are outside the defined program bounds, it crashes tdue to illegal values being written to the APIs and or being processed internal when coordinates are received from the API

Poor programming - contact the vendor and get them to correct the issue.
If the vendor is out of business, then you either have to re-engineering the interface or keep the display on the primary monitor.

 

[sactoking]

Originally posted by: Common Courtesy
The display front end may be trying to position itself to a given coordinate. When the coordinates of the second monitor are outside the defined program bounds, it crashes tdue to illegal values being written to the APIs and or being processed internal when coordinates are received from the API

Poor programming - contact the vendor and get them to correct the issue.
If the vendor is out of business, then you either have to re-engineering the interface or keep the display on the primary monitor.

Thanks. I figured it was sloppy programming, but wanted some validation.

 

[EagleKeeper]

Keep us posted