J
jhinrichsHH
Hello,
first poster here, i hope this is not a faq but i searched before and
haven't found anything. So:
I open a report via VBA like this:
DoCmd.OpenReport "rpAuslastungKonstrukteur", acViewPreview, ,
"ZeichnungPruefungDatum IS NULL"
I have a access project with SQL Server as backend. The report has a table
as datasource. In Access 2000 this works perfect.
Now my customer switched to Access 2003 and the report does not open anymore
(crash to desktop). If i open it manually, everything is fine. If i insert
the filter condition in the filter property it tells me, that it can't find
the table. If i insert it into the ServerFilter property, everything is fine.
But the VBA command does not work.
The project file is located on a network share. If i remove the readonly
file flag there, i can use the report, but my customer can't. Suspecting a
problem with access rights (cause i have write access and my customer not) i
moved the project file to his local disk and voila: everything works as
expected.
Now, can anyone tell me why write access to the project file is needed to
set a filter condition on a report and if there is any way around this? There
was a reason i write protected the file: It tends to get corrupted and
besides i would not want to have customers putting their hands on those forms
and reports. Not because of intellectual property, just to prevent them from
breaking something.
first poster here, i hope this is not a faq but i searched before and
haven't found anything. So:
I open a report via VBA like this:
DoCmd.OpenReport "rpAuslastungKonstrukteur", acViewPreview, ,
"ZeichnungPruefungDatum IS NULL"
I have a access project with SQL Server as backend. The report has a table
as datasource. In Access 2000 this works perfect.
Now my customer switched to Access 2003 and the report does not open anymore
(crash to desktop). If i open it manually, everything is fine. If i insert
the filter condition in the filter property it tells me, that it can't find
the table. If i insert it into the ServerFilter property, everything is fine.
But the VBA command does not work.
The project file is located on a network share. If i remove the readonly
file flag there, i can use the report, but my customer can't. Suspecting a
problem with access rights (cause i have write access and my customer not) i
moved the project file to his local disk and voila: everything works as
expected.
Now, can anyone tell me why write access to the project file is needed to
set a filter condition on a report and if there is any way around this? There
was a reason i write protected the file: It tends to get corrupted and
besides i would not want to have customers putting their hands on those forms
and reports. Not because of intellectual property, just to prevent them from
breaking something.