Viewing 15 posts - 2,236 through 2,250 (of 3,366 total)
I am assuming you are missing the GDR RTM download and install which gives you more options. And yes you still need SMS.
February 18, 2009 at 3:39 pm
it is an access database linked to a sharepoint list.
When last I checked a SharePoint List is a reference type so again I will not tell person with a...
February 18, 2009 at 3:29 pm
No we are not because using Sharepoint list require an adpter so you should have added that and I would not have spent a whole day trying to fix platform...
February 18, 2009 at 2:57 pm
I think your imported 32bits package is creating confusion so you need to delete everything related to it because in a 64bits box the only JET you get is a...
February 18, 2009 at 2:37 pm
Go to Server object in SMS you will see the linked server configuration tool in security you have some options.
One of the options is be made without a security context.
February 18, 2009 at 2:33 pm
Linked table require configurations and security or no security with defining linked server. And you also did not add SharePoint which may not allow Access. So I have...
February 18, 2009 at 2:26 pm
In my box both ODBC and OLE DB will take you to a point you can add your database file which will let the system know you are using JET....
February 18, 2009 at 2:05 pm
I am running Team Suites which includes all team editions including Database edition and don't let them fool you most multi language development I would use SMS, parsing the code...
February 18, 2009 at 1:23 pm
What Steve was saying is in the security section of linked server you can choose to run it without security.
Glad to see your problem is resolved.
February 18, 2009 at 1:13 pm
When you right click to add connection choose new and go to the types of connections and choose ODBC not OLE DB because that gives you Access as one of...
February 18, 2009 at 1:02 pm
Per the thread below you have not configured link server with the relevant permissions needed to run the code in the remote server. That is the account in one...
February 18, 2009 at 12:34 pm
What the error is saying is the job is running in the context of the Agent using network service account which cannot connect to the remote server. The reason...
February 18, 2009 at 12:16 pm
SQL Server Agent Log on as NT AUTHORITY/Network service
Change the above account to local systems and it will run but it is high permission account.
February 18, 2009 at 11:54 am
These three links covers all you will need please read all before doing any more development because Microsoft have covered what you need to know about development in 64bits box...
February 18, 2009 at 11:18 am
I just checked my 2005 BIDs there is place for you to add the x86 DSN I posted and use the steps posted by the other user relevant to 2005.
February 18, 2009 at 10:38 am
Viewing 15 posts - 2,236 through 2,250 (of 3,366 total)