Sunday, March 25, 2012
Access connectivity to SQL Tables (Urgent)
computers, will be able to link (over the Internet) to the tables in our SQL
Server (2000) database on your server.If the clients running Access can access the SQL Server,
including the proper ports being open, authentication issues
resolved then yes you could link the tables. Whether you
would want to or not is a different story.
-Sue
On Fri, 7 Apr 2006 02:26:03 -0700, pcsmitpra
<pcsmitpra@.discussions.microsoft.com> wrote:
>Please let me know whether Microsoft Access(2000), running on our office
>computers, will be able to link (over the Internet) to the tables in our SQ
L
>Server (2000) database on your server.
Access Combo Box Linked to Stored Proc
Access cannot see MSDE when network cable disonnected
connection tool cannot see any servers even thought I know they are
there. The data link properties dialog does not see them. Also my data
entry program also cannot see them but is using sqldmo to list the
servers. However my SQL Service manager (inside my task bar) Can see
them. Any pointers on how to let the access project or the sqldmo
objects see the servers when they are disconnected. I even tried using
ODBC with no luck.
Thanks for any help.
Shane
Hello,
Personnaly, I use the following
Dim ListSvr As NameList
Set ListSvr = SQLDMO.ListAvailableSQLServers
' I add the servers to a collection after removing the ones I don't want
to show
' After that,
Set oServer = New SQLDMO.SQLServer2
Set ListSvr = oServer.ListInstalledInstances
' This function always work but only for the local instances (named or not)
' I add the needed servers to the other collection but I don't put the
servers already listed before
Marc Allard
Allcomp
Shane Lim wrote:
> When my users are in the field and try to switch databases the
> connection tool cannot see any servers even thought I know they are
> there. The data link properties dialog does not see them. Also my data
> entry program also cannot see them but is using sqldmo to list the
> servers. However my SQL Service manager (inside my task bar) Can see
> them. Any pointers on how to let the access project or the sqldmo
> objects see the servers when they are disconnected. I even tried using
> ODBC with no luck.
> Thanks for any help.
> Shane
>
|||That is PERFECT!!
On Fri, 25 Feb 2005 10:39:39 +0100, Allcomp <marc@.nospam.allcomp.be>
wrote:
[vbcol=seagreen]
>Hello,
>Personnaly, I use the following
>Dim ListSvr As NameList
>Set ListSvr = SQLDMO.ListAvailableSQLServers
>' I add the servers to a collection after removing the ones I don't want
>to show
>' After that,
>Set oServer = New SQLDMO.SQLServer2
>Set ListSvr = oServer.ListInstalledInstances
>' This function always work but only for the local instances (named or not)
>' I add the needed servers to the other collection but I don't put the
>servers already listed before
>Marc Allard
>Allcomp
>
>Shane Lim wrote:
Tuesday, March 20, 2012
Access 2003 with SQL Express 2005
I am a fresher in using SQL with access.
I am using a code in Ms access to link a table that is in Sql express 2005.
I use this linked table name to download records to the local Access table.
The link is then dropped in Access.
Is there any way to write back records into the linked Sql table from Access.
It does not allow me to delete / add / modify records of a linked table.
How can I do this.
Thanks
Sjohn
YOU will need to specify the primary key on the linked server table that exists in SQL Server. This information is automatically created by default.HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
sql
Access 2003 Project Connecting to SQL 2000 & 2005 Servers
We have an Access 2003 Project that it's primary server is a SQL 2000 server. When I link a table to the 2000 server and execute the view, I get data with no problem. I link a table to the 2005 server and execute the view...once again, no problem. However, if I try to write a query to pull data from both views......times out. I have changed the timeout value to "0" and never returns the data.
So then I created a new Access 2003 Project to use the 2005 as the primary server. Once again I create a linked table and execute the view on the SQL 2000 server and it works just fine. Then create a linked table to the 2005 server and the view works just fine. However, here's the difference. When I try to create a query to pull data from both views, I get:
- This version of Microsoft Office Access doesn’t support design changes with the version of Microsoft SQL Server your Access project is connected to. See the Microsoft Office Update Web site for the latest information and downloads. Your design changes will not be saved.
- You have connected to a version of SQL Server later than SQL Server 2000. The version of Visual Studio or Access that you are using was released before the version of SQL Server to which you are connected. For this reason, you might encounter problems. Please check with Microsoft to see if there is a service pack that you should apply to Visual Studio or Office in order to get support for the version of SQL Server to which you are connected. You can continue but any new object types might not be enumerated, and it will not be possible to save any objects or database diagrams that you create using the Visual Database Tools.
Any assistance would be GREATLY appreciated. I'm stuck and wish I could make this happen.
PS:....
The version of Access 2003 specifically is: Microsoft ? Office Access 2003 (11.6566.6568) SP2
I've even made two linked tables to the 2005 server and executed each view by themselves and it worked fine. However, if I try to create a query off of those linked tables, same errors just posted above.
I'm afraid that Access ADPs aren't going to work all that smoothly with SQL Server 2005--they are created for SQL Server 2000 and earlier. If you're creating a new app, it's recommended that you use an mdb with linked tables because it gives you more flexibility. ADPs were designed around the scenario that you would connect to *one* SQL Server database, not multiple databases. One option if you must use ADPs is to create views to access data in another database. You can then use those views in your Access FE.
--Mary
Monday, March 19, 2012
Access .mdb link to SQL Server 2000
Can anyone help - I've got an Access 2002 Database which links to our SQL Se
rver 2000 Database via an ODBC connection. The connection is set to use SQL
Server authentication which works fine for myself but not for a domain user
who needs this.
When I launch the Database and run the query which links the Database I get
"Connection failed: Sqlstate: 28000 Sql server error: 18456 Microsoft odbc
sql server driver sql server login failed for user null; reason, not associa
ted with a trusted sql server.
I've installed the latest version of MDAC 2.8 which didn't help. When I get
the error message up, I can get round the problem by unticking the "Use Tru
sted Connection" and then inputting the SQL Server password for the user but
it should just run the query and display in Access.
Any advice would be great.
Thanks,
MichaelYou'll need to create a security group for the users that require access to
SQL Server. Give that security group necessary permissions to the database a
nd your trusted connection should work.
Adding the security group is somewhat documented here: http://support.microsoft.co
..Ben-us%3B889615
Steve
"Hoja, Michael" <Michho@.oink.co.uk> wrote in message news:uxRarDDFFHA.1260@.T
K2MSFTNGP12.phx.gbl...
Hi,
Can anyone help - I've got an Access 2002 Database which links to our SQL Se
rver 2000 Database via an ODBC connection. The connection is set to use SQL
Server authentication which works fine for myself but not for a domain user
who needs this.
When I launch the Database and run the query which links the Database I get
"Connection failed: Sqlstate: 28000 Sql server error: 18456 Microsoft odbc
sql server driver sql server login failed for user null; reason, not associa
ted with a trusted sql server.
I've installed the latest version of MDAC 2.8 which didn't help. When I get
the error message up, I can get round the problem by unticking the "Use Tru
sted Connection" and then inputting the SQL Server password for the user but
it should just run the query and display in Access.
Any advice would be great.
Thanks,
Michael|||Thanks Steve - I'll give that a go and let you know how I get on.
"Steve Thompson" <stevethompson@.nomail.please> wrote in message news:OH$IIvO
GFHA.936@.TK2MSFTNGP12.phx.gbl...
You'll need to create a security group for the users that require access to
SQL Server. Give that security group necessary permissions to the database a
nd your trusted connection should work.
Adding the security group is somewhat documented here: http://support.microsoft.co
..Ben-us%3B889615
Steve
"Hoja, Michael" <Michho@.oink.co.uk> wrote in message news:uxRarDDFFHA.1260@.T
K2MSFTNGP12.phx.gbl...
Hi,
Can anyone help - I've got an Access 2002 Database which links to our SQL Se
rver 2000 Database via an ODBC connection. The connection is set to use SQL
Server authentication which works fine for myself but not for a domain user
who needs this.
When I launch the Database and run the query which links the Database I get
"Connection failed: Sqlstate: 28000 Sql server error: 18456 Microsoft odbc
sql server driver sql server login failed for user null; reason, not associa
ted with a trusted sql server.
I've installed the latest version of MDAC 2.8 which didn't help. When I get
the error message up, I can get round the problem by unticking the "Use Tru
sted Connection" and then inputting the SQL Server password for the user but
it should just run the query and display in Access.
Any advice would be great.
Thanks,
Michael
Access .mdb link to SQL Server 2000
Can anyone help - I've got an Access 2002 Database which links to our SQL Server 2000 Database via an ODBC connection. The connection is set to use SQL Server authentication which works fine for myself but not for a domain user who needs this.
When I launch the Database and run the query which links the Database I get "Connection failed: Sqlstate: 28000 Sql server error: 18456 Microsoft odbc sql server driver sql server login failed for user null; reason, not associated with a trusted sql server.
I've installed the latest version of MDAC 2.8 which didn't help. When I get the error message up, I can get round the problem by unticking the "Use Trusted Connection" and then inputting the SQL Server password for the user but it should just run the query and display in Access.
Any advice would be great.
Thanks,
Michael
You'll need to create a security group for the users that require access to SQL Server. Give that security group necessary permissions to the database and your trusted connection should work.
Adding the security group is somewhat documented here: http://support.microsoft.com/default...en-us%3B889615
Steve
"Hoja, Michael" <Michho@.oink.co.uk> wrote in message news:uxRarDDFFHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi,
Can anyone help - I've got an Access 2002 Database which links to our SQL Server 2000 Database via an ODBC connection. The connection is set to use SQL Server authentication which works fine for myself but not for a domain user who needs this.
When I launch the Database and run the query which links the Database I get "Connection failed: Sqlstate: 28000 Sql server error: 18456 Microsoft odbc sql server driver sql server login failed for user null; reason, not associated with a trusted sql server.
I've installed the latest version of MDAC 2.8 which didn't help. When I get the error message up, I can get round the problem by unticking the "Use Trusted Connection" and then inputting the SQL Server password for the user but it should just run the query and display in Access.
Any advice would be great.
Thanks,
Michael
|||Thanks Steve - I'll give that a go and let you know how I get on.
"Steve Thompson" <stevethompson@.nomail.please> wrote in message news:OH$IIvOGFHA.936@.TK2MSFTNGP12.phx.gbl...
You'll need to create a security group for the users that require access to SQL Server. Give that security group necessary permissions to the database and your trusted connection should work.
Adding the security group is somewhat documented here: http://support.microsoft.com/default...en-us%3B889615
Steve
"Hoja, Michael" <Michho@.oink.co.uk> wrote in message news:uxRarDDFFHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi,
Can anyone help - I've got an Access 2002 Database which links to our SQL Server 2000 Database via an ODBC connection. The connection is set to use SQL Server authentication which works fine for myself but not for a domain user who needs this.
When I launch the Database and run the query which links the Database I get "Connection failed: Sqlstate: 28000 Sql server error: 18456 Microsoft odbc sql server driver sql server login failed for user null; reason, not associated with a trusted sql server.
I've installed the latest version of MDAC 2.8 which didn't help. When I get the error message up, I can get round the problem by unticking the "Use Trusted Connection" and then inputting the SQL Server password for the user but it should just run the query and display in Access.
Any advice would be great.
Thanks,
Michael
Saturday, February 11, 2012
About dynamic URL link
custom assembly. However instead of generating the link each time the link is
clicked. The function only called once when the report is generated.
Therefore that link always return the same value. How can i implement this?
Thank you veru much.You can put per-report initialization in the OnInit() event in the Code
property of the report.
--
This post is provided 'AS IS' with no warranties, and confers no rights. All
rights reserved. Some assembly required. Batteries not included. Your
mileage may vary. Objects in mirror may be closer than they appear. No user
serviceable parts inside. Opening cover voids warranty. Keep out of reach of
children under 3.
"mcngan" <mcngan@.discussions.microsoft.com> wrote in message
news:16560A52-A252-4796-AAA3-CE8755473631@.microsoft.com...
> I want the URL link to be generated dynamically by a function written in a
> custom assembly. However instead of generating the link each time the link
is
> clicked. The function only called once when the report is generated.
> Therefore that link always return the same value. How can i implement
this?
> Thank you veru much.