-
Dear All,
I need help badly.
Question I
I always do my report design on Crystal Report. And the version that I use is Crystal Report ver. 7.0
No problem at all in design time or coding time. But one thing that getting on my nerves. My crystal doesn't want to print out to my printer.
At the first time, when I design it, and try it, it will preview on my screen, and then when I want to print it out, it's okay, my report will print out on my printer.
But, don't know why and how, yesterday, my report didn't want to print out (only preview on screen, but when I want to print it out, it didn't come out on my printer.
Can anybody help me ???
Question II
I already ask about this here, but never got the answer till now. I have a database on SQL Server (ver. 7.0). At the first time when I create the database, I already set the transaction log size into 80 MB, but now I think it's too big just for a transaction log. Now, I want to change it to 20 MB. But, an error occurs. It said that I can't set the size to the little one, I should set to the bigger one.
Could anybody tell me how to change the size into the smaller one ???
Any help will be appreciated. I need it badly. Help...
Thx in advice.
Regards,
Wen Lie
-
Question 1
Printers are funny things... sometimes they just don't want to print. It could have been anything from a blocked buffer to an uninitialized port.
If the problem was a "once off" and hasn't occured since then I wouldn't worry about it... if it is something that happens regularly I would re-install the print drivers and see how things go
Question 2
The first thing you have to do is "clear" the Transaction Log. You can't decrease its size while it is larger than the size you want. It will give you a warning but unless you are unsure if your database is in a nice and tidy state (ie hasn't been corrupted recently) then clear it.
Once that is done you can choose to reduce the size of this Transaction File. I wouldn't really recommend going below 50MB unless you have some serious space shortages as SQL is very hungry when it comes to this log file.
THe other thing you might conisder doing is asking SQL Server to clear the Transaction Log at "breakpoints". This will make sure the log file doesn't fill up and keeps your database running smoothly. DOn't ask me where to find this as I haven't looked at SQL 7 for this yet though its in the properties for SQL 6.5
