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.

Hi

Hi,

I have setup a linked server to a DB2 database using "Microsoft OLE DB Provider for ODBC Drivers",

the connections works fine i am able to run select queries.

but the number of rows returned from the two following statements are different.

select * from linkedserver...tablename

select count(*) from linkedserver...tablename

e.g. The First statement returns 116 rows, whereas the second query returns count as 144....

I am a bit confused ?

could anybody think of any possible reasons..

Cheers

ARAW012

Hi,

which SQL Server version are you using ? There was an issue with SQL Server 2000. Are you able to trace the queries that are actually executed at the DB2 database ? Did you already try to use the OPENQUERY method to pass the query (without any refactoring through the driver stack) through to the DB2 instance ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

i am using SQL server 2005 , and i am using the OPENQUERY method.

I only have read access to the DB2 database.

Thanks

|||The openquery and the "normal" Select behave different, because the OPENQUERY will issue a pass-through to the server instead of doing the interpreted Select query through the driver. So the results can differ according to the changes the driver will do in the middle. Perhaps someone with additional DB2 knowledge can help you here.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Help: Query Timeout Expired

Hi,
I have a long running view (counting over 2,000,000 records) that regurns
"[ODBC SQL Server Driver] Timeout Expired" error after about 30 seconds.
Can somebody tell me how to increase the timeout period for running View?
Thanks in advance.
Regards
YeeYee,
were are you running the view from , EM? If you are don't. Try running it
from QA.
Timeouts are a client connection issue and can be adjusted via your ODBC
connection details, they are not a server problem.
I hope this helps
regards
Greg O MCSD
http://www.ag-software.com/ags_scribe_index.aspx. SQL Scribe Documentation
Builder, the quickest way to document your database
http://www.ag-software.com/ags_SSEPE_index.aspx. AGS SQL Server Extended
Property Extended properties manager for SQL 2000
http://www.ag-software.com/IconExtractionProgram.aspx. Free icon extraction
program
http://www.ag-software.com. Free programming tools
"Yee CN" <nospamxx_cn.yee@.attic-solutions.com> wrote in message
news:eZsXYag6DHA.2656@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have a long running view (counting over 2,000,000 records) that regurns
> "[ODBC SQL Server Driver] Timeout Expired" error after about 30 seconds.
> Can somebody tell me how to increase the timeout period for running View?
> Thanks in advance.
> Regards
> Yee
>|||Hi Yee:
The timeout may haeepn in several place. You can change it by T-SQL for
database or in the ADO for for ODBC.
Because you do not let us know what kind of operation you are doing.
What I can do is give some suggestion.
For database, you can type "timeout" in book online then you can get
information of how to set the timeout property in diffirent situation
For ODBC you can see this link and see the timeout part.
ms-help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/dnodbc/html/odbcsql.htm
Best Wishes
Wei Ci Zhou|||I was running it in EM. Just tried with QA, still the same problem.
I was managed to get it to run once earlier on though. It seems that the
timing the first row got returned is important here.
Regards,
Yee
"Greg Obleshchuk" <greg-n-o-s-p-a-m-@.ag-s-o-f-t-w-a-r-e.com> wrote in
message news:eGGXBsg6DHA.2056@.TK2MSFTNGP10.phx.gbl...
> Yee,
> were are you running the view from , EM? If you are don't. Try running
it
> from QA.
> Timeouts are a client connection issue and can be adjusted via your ODBC
> connection details, they are not a server problem.
>
> --
> I hope this helps
> regards
> Greg O MCSD
> http://www.ag-software.com/ags_scribe_index.aspx. SQL Scribe
Documentation
> Builder, the quickest way to document your database
> http://www.ag-software.com/ags_SSEPE_index.aspx. AGS SQL Server Extended
> Property Extended properties manager for SQL 2000
> http://www.ag-software.com/IconExtractionProgram.aspx. Free icon
extraction
> program
> http://www.ag-software.com. Free programming tools
>
> "Yee CN" <nospamxx_cn.yee@.attic-solutions.com> wrote in message
> news:eZsXYag6DHA.2656@.TK2MSFTNGP11.phx.gbl...
> > Hi,
> >
> > I have a long running view (counting over 2,000,000 records) that
regurns
> > "[ODBC SQL Server Driver] Timeout Expired" error after about 30 seconds.
> >
> > Can somebody tell me how to increase the timeout period for running
View?
> >
> > Thanks in advance.
> >
> > Regards
> > Yee
> >
> >
>|||I was opening the view from Enterprise Manager, then from Query Analyser.
Both gives the same error. I tried various things suggested in the help
file, including using sp_configure.
I also found the following from book online. The error message is what I
got - but I could not find the Tool->option screen mentioned below. Can you
shed any light?
----
--
ODBC error text
[Microsoft][ODBC SQL Server Driver]Timeout expired.
Explanation
The timeout can occur when you're updating the database with any
Transact-SQL changes.
Action
a.. Try again later to save the diagram or selected tables.
b.. Save a change script and apply it to the database at a later time.
c.. Increase the SQL Query Time-out value and try to save the diagram or
selected tables again.
To increase the SQL Query Time-out value
1.. From the Tools menu, choose Options.
2.. In the left pane, click Data Tools, and then click Data View.
3.. Type a new value in the SQL query time-out box.
----
--
Also the link that you suggested:
ms-help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/dnodbc/html/odbcsql.htm
- can you tell me how to get there?
Thanks a lot for your help.
Best regards,
Yee
"Wei Ci Zhou" <weicizhou@.hotmail.com.discuss> wrote in message
news:eBoSXfh6DHA.3008@.TK2MSFTNGP09.phx.gbl...
> Hi Yee:
> The timeout may haeepn in several place. You can change it by T-SQL
for
> database or in the ADO for for ODBC.
> Because you do not let us know what kind of operation you are doing.
> What I can do is give some suggestion.
> For database, you can type "timeout" in book online then you can get
> information of how to set the timeout property in diffirent situation
> For ODBC you can see this link and see the timeout part.
> Best Wishes
> Wei Ci Zhou
>

Help: Query Timeout Expired

Hi,
I have a long running view (counting over 2,000,000 records) that regurns
"[ODBC SQL Server Driver] Timeout Expired" error after about 30 seconds.
Can somebody tell me how to increase the timeout period for running View?
Thanks in advance.
Regards
YeeYee,
were are you running the view from , EM? If you are don't. Try running it
from QA.
Timeouts are a client connection issue and can be adjusted via your ODBC
connection details, they are not a server problem.
I hope this helps
regards
Greg O MCSD
http://www.ag-software.com/ags_scribe_index.aspx. SQL Scribe Documentation
Builder, the quickest way to document your database
http://www.ag-software.com/ags_SSEPE_index.aspx. AGS SQL Server Extended
Property Extended properties manager for SQL 2000
http://www.ag-software.com/IconExtractionProgram.aspx. Free icon extraction
program
http://www.ag-software.com. Free programming tools
"Yee CN" <nospamxx_cn.yee@.attic-solutions.com> wrote in message
news:eZsXYag6DHA.2656@.TK2MSFTNGP11.phx.gbl...

quote:

---

> Hi,
> I have a long running view (counting over 2,000,000 records) that regurns
> "[ODBC SQL Server Driver] Timeout Expired" error after about 30 seconds.
> Can somebody tell me how to increase the timeout period for running View?
> Thanks in advance.
> Regards
> Yee
>

---

|||Hi Yee:
The timeout may haeepn in several place. You can change it by T-SQL for
database or in the ADO for for ODBC.
Because you do not let us know what kind of operation you are doing.
What I can do is give some suggestion.
For database, you can type "timeout" in book online then you can get
information of how to set the timeout property in diffirent situation
For ODBC you can see this link and see the timeout part.
ms-help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/dnodbc/html/odbcsql.htm
Best Wishes
Wei Ci Zhou|||I was running it in EM. Just tried with QA, still the same problem.
I was managed to get it to run once earlier on though. It seems that the
timing the first row got returned is important here.
Regards,
Yee
"Greg Obleshchuk" <greg-n-o-s-p-a-m-@.ag-s-o-f-t-w-a-r-e.com> wrote in
message news:eGGXBsg6DHA.2056@.TK2MSFTNGP10.phx.gbl...

quote:

---

> Yee,
> were are you running the view from , EM? If you are don't. Try running

---

it

quote:

---

> from QA.
> Timeouts are a client connection issue and can be adjusted via your ODBC
> connection details, they are not a server problem.
>
> --
> I hope this helps
> regards
> Greg O MCSD
> http://www.ag-software.com/ags_scribe_index.aspx. SQL Scribe

---

Documentation

quote:

---

> Builder, the quickest way to document your database
> http://www.ag-software.com/ags_SSEPE_index.aspx. AGS SQL Server Extended
> Property Extended properties manager for SQL 2000
> http://www.ag-software.com/IconExtractionProgram.aspx. Free icon

---

extraction

quote:

---

> program
> http://www.ag-software.com. Free programming tools
>
> "Yee CN" <nospamxx_cn.yee@.attic-solutions.com> wrote in message
> news:eZsXYag6DHA.2656@.TK2MSFTNGP11.phx.gbl...
regurns[QUOTE]
View?[QUOTE]
>

---

|||I was opening the view from Enterprise Manager, then from Query Analyser.
Both gives the same error. I tried various things suggested in the help
file, including using sp_configure.
I also found the following from book online. The error message is what I
got - but I could not find the Tool->option screen mentioned below. Can you
shed any light?
----
--
ODBC error text
[Microsoft][ODBC SQL Server Driver]Timeout expired.
Explanation
The timeout can occur when you're updating the database with any
Transact-SQL changes.
Action
a.. Try again later to save the diagram or selected tables.
b.. Save a change script and apply it to the database at a later time.
c.. Increase the SQL Query Time-out value and try to save the diagram or
selected tables again.
To increase the SQL Query Time-out value
1.. From the Tools menu, choose Options.
2.. In the left pane, click Data Tools, and then click Data View.
3.. Type a new value in the SQL query time-out box.
----
--
Also the link that you suggested:
ms-help://MS.VSCC.2003/MS.MSDNQTR.2003JUL.1033/dnodbc/html/odbcsql.htm
- can you tell me how to get there?
Thanks a lot for your help.
Best regards,
Yee
"Wei Ci Zhou" <weicizhou@.hotmail.com.discuss> wrote in message
news:eBoSXfh6DHA.3008@.TK2MSFTNGP09.phx.gbl...

quote:

---

> Hi Yee:
> The timeout may haeepn in several place. You can change it by T-SQL

---

for

quote:

---

> database or in the ADO for for ODBC.
> Because you do not let us know what kind of operation you are doing.
> What I can do is give some suggestion.
> For database, you can type "timeout" in book online then you can get
> information of how to set the timeout property in diffirent situation
> For ODBC you can see this link and see the timeout part.
> Best Wishes
> Wei Ci Zhou
>

---

HELP: ODBC Registry Error

Hi,
some registry entries about sql server odbc driver was accidently
deleted by me. now, in the driver page of odbc data source administor,
i can not found the sql server driver in the list. for the reason, the
SQL Server 2000 can not complete its installation normally, and the
problem is that i need to install the software.
i don't know how do i fix the error. i've already download a MDAC RTM
from microsoft, but it stop installation and report: MDAC 2.8 RTM is
incompatible with this version of Windows. All of its features are
currently part of Windows.
can anyone please help me ( my system is Windows XP )For what it's worth, here are the contents of a working Windows 2000
MDAC 2.8 SQL Server driver settings - obviously you need to tweak the
path to the DLL's according to your setup.
Windows Registry Editor Version 5.00
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODB
CINST.INI\SQL Server]
"UsageCount"=dword:00000007
"Driver"="C:\\WINNT\\System32\\SQLSRV32.dll"
"Setup"="C:\\WINNT\\System32\\SQLSRV32.dll"
"SQLLevel"="1"
"FileUsage"="0"
"DriverODBCVer"="03.50"
"ConnectFunctions"="YYY"
"APILevel"="2"
"CPTimeout"="60"

HELP: MFC ODBC SQL Server problems

I got a problem where in SQL Server a table has a column of type REAL & size
(precision) 4. It's meant to store double types for C++ variable values.
In SQL Server, the value 1E+10 translates to 10000000000 in C++ fine, via
MFC's CRecordset class (DBCORE.CPP). However any numbers above this value
translates to wrong numbers. Such as:
1.1E+10 => 10000000512
1.00001E+10 => 10000001024
1.01E+10 => 10099999744
1.0000001E+10 => 10000100352
Strange huh? Has anybody experienced this before? Does anyone know what is
wrong? I tried upgrading my SQL Server 2000 to SP4 and even upgraded MAC2.6
to SP2. Still no success.You should not use "Real" to handle a big number like "1E+10" since real
data type does not have enough precisions to do the job. If you change
the data type to "Float", you will have better chance to get the number
right. Or if you want to store "Exact" numbers, you should use "decimal"
as your data type.
Charles Zhang
http://www.speedydb.com
SpeedyDB ADO.NET is the fastest, most secure, and most flexible ADO.NET
Provider over Wide Area Netword (WAN).
Andrew Wan wrote:
> I got a problem where in SQL Server a table has a column of type REAL & si
ze
> (precision) 4. It's meant to store double types for C++ variable values.
> In SQL Server, the value 1E+10 translates to 10000000000 in C++ fine, via
> MFC's CRecordset class (DBCORE.CPP). However any numbers above this value
> translates to wrong numbers. Such as:
> 1.1E+10 => 10000000512
> 1.00001E+10 => 10000001024
> 1.01E+10 => 10099999744
> 1.0000001E+10 => 10000100352
> Strange huh? Has anybody experienced this before? Does anyone know what is
> wrong? I tried upgrading my SQL Server 2000 to SP4 and even upgraded MAC2.
6
> to SP2. Still no success.
>
>