Hide an ODBC connection?

We've purchased a 3rd party app that uses an Access db linked to SQL Server. Unfortunately, we've come to discover that a user of ours seems to know access and has decided to take report writing into their own hands.
We have the app and the access db on a server and a mapped a drive for each user.

Unfortunately, I can't lock down the ODBC connection because that would lock it down in the app. Someone suggested using a File DSN and removing the System DSN's off all users machines. I'm not too familiar with File DSN's and wanted to know if this would prevent users from creating their own Access mdb's linked to my server or not.

Any idea's are greatly appreciated.Dude,

Bad news :( - unless you can stop the end user from hacking the registry and prevent access to the odbcad32 (which you really can't lock out and have the machine access the server) there isn't much you can do AFAIK.

You didn't mention what OS's are in play. If you are a Win2k/WinXP shop you may be able to build a policy that limits the user from adding a new DSN, but I doubt even a file DSN will really stop him. If you go look in C:\Program Files\Common Files\ODBC\Data Sources All they really do is point to the system DSN. And he'll be able to pick it in Access.|||I figured the answer would go something like that.
Thank you anyways.

hidden lines at top of report

I've finally gotten my 1st report functional. Unfortunately, there is a huge
chunk of hidden lines -- blank lines -- at the top of the report. You see
my header, then a big blank space, scroll down and you get the data. I'm all
over the layout formatting but I"m just not finding it. Any thoughts?
-- LynnDoes anybody know what I could do to remove all the blank lines in between my
header and my report body?
-- Lynn
"Lynn" wrote:
> I've finally gotten my 1st report functional. Unfortunately, there is a huge
> chunk of hidden lines -- blank lines -- at the top of the report. You see
> my header, then a big blank space, scroll down and you get the data. I'm all
> over the layout formatting but I"m just not finding it. Any thoughts?
> -- Lynn|||Lynn,
I do not know if this is at all relevant in your case, but are you using
filters? If so, where are you filtering?
The reason that I ask is that I got this problem when I was filtering
results from my dataset, using a filter within a table group, rather than a
filter on the entire table itself. When I switched my filter to the latter,
the problem disappeared.
Long shot I know, but I thought it was worth mentioning just in case.
Ed Allison
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:31CDBFAF-DCEF-444B-9437-45D2A639BFFC@.microsoft.com...
> Does anybody know what I could do to remove all the blank lines in between
> my
> header and my report body?
> -- Lynn
>
> "Lynn" wrote:
>> I've finally gotten my 1st report functional. Unfortunately, there is a
>> huge
>> chunk of hidden lines -- blank lines -- at the top of the report. You
>> see
>> my header, then a big blank space, scroll down and you get the data. I'm
>> all
>> over the layout formatting but I"m just not finding it. Any thoughts?
>> -- Lynn|||Do you have the header size only big enough to fit what your header is? Is
whatever you used in your report body (table,list) started all of the way at
the top, right under where your header ends? If you leave any white space in
the grid, it seems to use that. Are the lines hidden because you hid them
intentionally, or is it a spacing issue?
"Lynn" wrote:
> I've finally gotten my 1st report functional. Unfortunately, there is a huge
> chunk of hidden lines -- blank lines -- at the top of the report. You see
> my header, then a big blank space, scroll down and you get the data. I'm all
> over the layout formatting but I"m just not finding it. Any thoughts?
> -- Lynn|||Thank you, Ed. Unfortunately, no, I am not using filters. But, I will keep
this information handy, should that change.
-- Lynn
"Ed Allison" wrote:
> Lynn,
> I do not know if this is at all relevant in your case, but are you using
> filters? If so, where are you filtering?
> The reason that I ask is that I got this problem when I was filtering
> results from my dataset, using a filter within a table group, rather than a
> filter on the entire table itself. When I switched my filter to the latter,
> the problem disappeared.
> Long shot I know, but I thought it was worth mentioning just in case.
> Ed Allison
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:31CDBFAF-DCEF-444B-9437-45D2A639BFFC@.microsoft.com...
> > Does anybody know what I could do to remove all the blank lines in between
> > my
> > header and my report body?
> > -- Lynn
> >
> >
> > "Lynn" wrote:
> >
> >> I've finally gotten my 1st report functional. Unfortunately, there is a
> >> huge
> >> chunk of hidden lines -- blank lines -- at the top of the report. You
> >> see
> >> my header, then a big blank space, scroll down and you get the data. I'm
> >> all
> >> over the layout formatting but I"m just not finding it. Any thoughts?
> >> -- Lynn
>
>|||When I say 'hidden lines', I just mean there's a huge space up there -
between the header and the actual report body. I put my mouse there and
scrolled down, finding it highlighted the empty lines...so I just called them
'hidden'. And to my knowledge, the header is only big enough to fit what
I've given it. The body, too, as I've started it right at the top. I just
don't know what is causing this.
-- Lynn
"KimB" wrote:
> Do you have the header size only big enough to fit what your header is? Is
> whatever you used in your report body (table,list) started all of the way at
> the top, right under where your header ends? If you leave any white space in
> the grid, it seems to use that. Are the lines hidden because you hid them
> intentionally, or is it a spacing issue?
> "Lynn" wrote:
> > I've finally gotten my 1st report functional. Unfortunately, there is a huge
> > chunk of hidden lines -- blank lines -- at the top of the report. You see
> > my header, then a big blank space, scroll down and you get the data. I'm all
> > over the layout formatting but I"m just not finding it. Any thoughts?
> > -- Lynnsql