We are having a slight problem at work with Sage since we upgraded to SP1.

SP1 upgraded on tuesday to our laptops which run Sage Line 50 and since then we can't print invoices as there is a margin error that we don't seem to be able to fix.

We have tried re-installing sage and this doesn't cure the problem.

Anybody got any ideals?

Cheers

One isn't set to letter and the other to A4 is it?

One isn't set to letter and the other to A4 is it?

Set to A4 and tried to adjust margins to same as our comp which runs XP but it won't save them.

It only started playing up after SP1 was installed.

Sage is old version and we don't pay for support.

Had a quick look for any fix,but didn't find any.

Try uninstalling the printer driver and reinstalling it?

Which make of printer is it? Can you get one from the manufacturer rather than the built in windows one?

Try uninstalling the printer driver and reinstalling it?

Which make of printer is it? Can you get one from the manufacturer rather than the built in windows one?

I should have made myself clearer.

If i go into review of the document to check what the printed doc will be,it displays the document paper but not the details (what the ink will print).

It works ok printing stock sheets etc...but when trying to print anything on sage invoice paper then it appears blank.

Have unistall sage,re-installed and them restored data from pc which is running XP/Sage and everything restores but won't print invoices still!

Might be worth paying for support or googling the problem!

Older versions of Sage do not work properly with Line 50. Upgrade time I am afraid. Don't want to sound uppity but a firms financial information is far to valuable to skip on upgrade costs.

Could be that the SP1 update has replaced some of the printer driver files, I would reload these first.

Sage has been working fine till sp1 was loaded.

I may unistall sp1 and see how that goes.

We have looked at buying newer version of sage and may have to,but if we can do without it for now saving a grand.

Just wondered if anybody have had the same problem,but doesn't look like it.