We have seen this. We examined the data off the clients site and could not duplicate the problem. The problem is not in the data. It has something to do with the environment. We dump/loaded the data and restarted the SQL Server and the GL Budget screen started working. 

thanks much; will dump/load into new company DB and see what happens - very weird stuff

last thing RVSPY said was reading GLAFS and then it stopped recording activity

yep, that seems to fix it - weird

here is the wrap up

#1  DBDump/Load into company of same abbreviation - no fix

#2 DBDump/Load into company of different abbreviation - fix

for #1

Found out _P.ism file messed up and scanisam did not detect; had Sage make new one and FIXED.

I think that budget screen tries to prepare for printing before it comes up - and it was messed up for printing.

thanks all

here is the wrap up

#1  DBDump/Load into company of same abbreviation - no fix

#2 DBDump/Load into company of different abbreviation - fix

for #1

Found out _P.ism file messed up and scanisam did not detect; had Sage make new one and FIXED.

I think that budget screen tries to prepare for printing before it comes up - and it was messed up for printing.

thanks all