J
James
I have posted to these newsgroups many times, and have had many experienced
programmers help my greatly. However, I am still drawn between some issues.
I am trying to print 2 out of my 30 reports to one specific printer (this
could change depending on the user). I know about the Printer APIs and here
are my issues.
1) There is only an option to change the printer, not the printer margins
and paper size.
2) The API for Access 2000 errors out and locks Access.
3) The APIs for Access 2002-03 are not backward compatible with 2000.
(Which is not a problem because I can tell them that they will have to have
2002 + to run the database.
The user originally could not view the report only print it from the form
(when I was using the print APIs). I decided to change this because the user
might have a different printer with different margins (or not have the SPs
installed which would change the printer margins sometimes). Nonetheless, I
like giving the user these privileges. My dilemma is you can only have an
mdb file or else the changes to the report would not be saved (am I correct).
So with that said...is it a bad thing to have a mdb file because it could
become corrupt and/or start to run slower? If I keep it an mdb do I need to
allow the user to compact and repair? Are there any better solutions to my
problem?
On some computers the db window opens with the mdb even though I have told
access not to open it. This is my main reason why I would like to make it an
mde file!
programmers help my greatly. However, I am still drawn between some issues.
I am trying to print 2 out of my 30 reports to one specific printer (this
could change depending on the user). I know about the Printer APIs and here
are my issues.
1) There is only an option to change the printer, not the printer margins
and paper size.
2) The API for Access 2000 errors out and locks Access.
3) The APIs for Access 2002-03 are not backward compatible with 2000.
(Which is not a problem because I can tell them that they will have to have
2002 + to run the database.
The user originally could not view the report only print it from the form
(when I was using the print APIs). I decided to change this because the user
might have a different printer with different margins (or not have the SPs
installed which would change the printer margins sometimes). Nonetheless, I
like giving the user these privileges. My dilemma is you can only have an
mdb file or else the changes to the report would not be saved (am I correct).
So with that said...is it a bad thing to have a mdb file because it could
become corrupt and/or start to run slower? If I keep it an mdb do I need to
allow the user to compact and repair? Are there any better solutions to my
problem?
On some computers the db window opens with the mdb even though I have told
access not to open it. This is my main reason why I would like to make it an
mde file!