Hi guys,
This is a tough one and any help would be greatly appreciated. Firstly I have a database that users can create (preformatted) letters on. just fill in a couple of boxes and whamo instant letter. Now from there I have created reports to match the letters and just use queries to get the "fill-in" info to stick on the report. I then print out the report on letter head...now I have a letter, GET IT?. So my problem is this...the database is rather large and supports about 200 users (not all at the same time). When the "Letters" are printed out I will be missing a couple (I didn't even realize this was a problem until someone stated "This stack isn't high enough to be all the letters".) So now I stuck, I have about 200 users who were use to hand writing letters who are now use to just a couple keystrokes and a click ->they wil not be happy if this database goes away. I was thinking it may be a printer problem but then I thought "No wait I am losing entire "Letters" (letters are 2 to 3 pages long) not just a page here and there. So that is why I believe it to be an access problem. I am running Acess97 on WinNT setup. I am printing to a local printer (with 32MB on board memory). I have changed it from spooling to print direct trying to stop this mess; it really doesn't seem to make a difference. There is no discernable pattern on the pages that are lost. I thought maybe at first that some users were creating letter while the report was printing but before my update query had run, but this is not the case. So now after investigating all possble problems I still have no answer. I would appreciate any and all suggestions, even if you are not sure that it would help or not.
Thanks
Scotty :
This is a tough one and any help would be greatly appreciated. Firstly I have a database that users can create (preformatted) letters on. just fill in a couple of boxes and whamo instant letter. Now from there I have created reports to match the letters and just use queries to get the "fill-in" info to stick on the report. I then print out the report on letter head...now I have a letter, GET IT?. So my problem is this...the database is rather large and supports about 200 users (not all at the same time). When the "Letters" are printed out I will be missing a couple (I didn't even realize this was a problem until someone stated "This stack isn't high enough to be all the letters".) So now I stuck, I have about 200 users who were use to hand writing letters who are now use to just a couple keystrokes and a click ->they wil not be happy if this database goes away. I was thinking it may be a printer problem but then I thought "No wait I am losing entire "Letters" (letters are 2 to 3 pages long) not just a page here and there. So that is why I believe it to be an access problem. I am running Acess97 on WinNT setup. I am printing to a local printer (with 32MB on board memory). I have changed it from spooling to print direct trying to stop this mess; it really doesn't seem to make a difference. There is no discernable pattern on the pages that are lost. I thought maybe at first that some users were creating letter while the report was printing but before my update query had run, but this is not the case. So now after investigating all possble problems I still have no answer. I would appreciate any and all suggestions, even if you are not sure that it would help or not.
Thanks
Scotty :
