ODBC Connector and MS-Access

[relemon]

I am trying to retrieve data using the ODBC connector for Service-Now. I can successfully pull data using iSQL and Microsoft Excel; however, when I try to retrieve data using MS-Access, the query returns the data but every field is populated with #DELETED. Is MS-Access supported at this time?

Thanks.

[Christopher_Mal]

relemon,

I got this from the MS support site:

Retrieve records with an SQL pass-through query. An SQL pass-through query is not updateable, and therefore does not cause "#Delete" errors.

http://support.microsoft.com/kb/128809

I don't know if this will help or not. I unfortunately don't have a MS-Access license or the software installed to try it out.

[relemon]

Unfortunately this did not work. Using a pass through query has the same results. I did a simple query to select incidents created on

SELECT OAUSER_incident.number, OAUSER_incident.opened_at
FROM OAUSER_incident
WHERE (((OAUSER_incident.opened_at)>#10/1/2011#));

I am able to use queries to update tables in my database. I just can not view the data.

[JoeyMart]

I have seen this happen when linking the table in Access. Since the ODBC driver is strictly read-only, linking a table in Access is not going to work. You should be able to import the table (which actually copies the data into a new table within Access) and not receive the error. If Access is asking you for a unique identifier, it is trying to link the table. In Access 2010 the process is:
External Data > ODBC > Import

That being said, Access has some intrinsic problems that make it behave erratically with the ServiceNow ODBC driver. In my experience, it works fine when the result set is less than 1500 rows, but once it gets any larger than that, you may start to see some strange errors.

[lionel]

Hi all

Work around about that is not to select any index

If you read "#Deleted" errors with linked ODBC tables, the problem come from index and maintenance of this index

so when you do not choose any index, it's working fine.