Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
sthompson  
#1 Posted : Thursday, June 21, 2012 7:38:21 PM(UTC)
sthompson
Rank: Newbie

Reputation:

Groups: Registered
Posts: 0
Location: Whitehorse

Hello, 

Everytime I output tables into excel (Chem Table), I get this error "10460 General ODBC Error", and the table is blank.  How can I resolve this?

Thanks,

Sarah

Support  
#2 Posted : Thursday, June 21, 2012 8:05:18 PM(UTC)
Support
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 259
Location: Ballina

Was thanked: 8 time(s) in 8 post(s)

Hello,

If you deselect the "Environmental Guidelines" checkbox prior to export (so none are exported) do you get the error.  If not, try exporting with particular guidelines to see if it is realted to one in particular. 

If it's not related to that, try filtering the data until you don't get it so you can isolate where in the data an issue might be.

It is most likely to be unusual characters in the name.  An apostrophie(') can also cause problems sometimes.  

You can view/edit your environmental standards under Data Tables - zRef_Environmental_Standards.

Sincerely,

Alex

sthompson  
#3 Posted : Friday, June 22, 2012 7:56:28 PM(UTC)
sthompson
Rank: Newbie

Reputation:

Groups: Registered
Posts: 0
Location: Whitehorse

I don't think the problem is based on the data in ESdat.  I was able to output the table on a co-worker's computer, but not my own.

Support  
#4 Posted : Friday, June 22, 2012 9:05:35 PM(UTC)
Support
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 259
Location: Ballina

Was thanked: 8 time(s) in 8 post(s)

Hello,

A few more questions for you, if that is OK.

Did it just start happening?

Did anything change on your PC that you are aware of between when it wasn't happening, and when it  started?

Does it happen for all projects? If not is there any pattern you've observed.

As producing the same export on another users PC seems to work, it looks to be related to the PC rather than a particular dataset.  Have you tried uninstalling and reinstalling ESdat on your PC?  Also trying a repair of Office (under Control Panel).  Does you co-worker have a similar PC setup (Windows and Office version?)

Alex

Edited by user Friday, June 22, 2012 9:06:14 PM(UTC)  | Reason: Not specified

Woodsda  
#5 Posted : Wednesday, June 27, 2012 3:11:46 AM(UTC)
Woodsda
Rank: Newbie

Reputation:

Groups: Registered
Posts: 0
Location: Melbourne

Hi Sarah, I too have been getting this error message in one of our offices. It first appeared when i was trying to run the example database tutorial. Have you tried loading the tutorial database and creating a table? If ESdat gives an error when working on the provided database, it does not appear to be related to my specific project data. Starting a new project and importing my data temporarily worked but I am getting the same error on a separate fresh project with no environmental guidelines.

I have already removed and reinstalled ESdat but that did not fix the problem. Any further diagnosis?

Thanks,

Dean

Support  
#6 Posted : Wednesday, June 27, 2012 10:37:01 PM(UTC)
Support
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 259
Location: Ballina

Was thanked: 8 time(s) in 8 post(s)

Hello Dean,

It appears from both posts that the issue isn't related to data, as Sarah can output the same data from a different PC.

Does logging in to Windows with a different username make any difference?

Does installing all Windows updates and running a repair on Excel make any difference?

Alex

 

 

Some other checks to try:

Warwick Wood  
#7 Posted : Friday, July 13, 2012 4:01:41 AM(UTC)
Warwick Wood
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 498
Man
Location: Byron Bay

Was thanked: 19 time(s) in 19 post(s)


We've determined that this issue is caused by an issue on the PC, even though it doesn't uniformly affect all databases used when on that PC.  It has only come to our attention recently, but is unrelated to any particular version of ESdat.  It is likely to be caused by some update patch for windows or Office/Excel, but we don't have any more specifics at this point.

Suggested actions are:

  •     Repair / Reinstall MS Office
  •     Repair MDAC (Microsoft Data Access Components), see http://support.microsoft.com/kb/899861 for details (instructions relate to XP, SP2, but are also applicable to other versions).  It is best to get IT input on doing this one.
  •     Try a different login on the same PC.

If anyone has any other observations that might help isolate the cause it would be much appreciated as we don't hav e a PC with the problem that we can play with.  Similarly any feedback as to the sucess of the above recommendations (or otherwise) is appreciated.

Regards,

Warwick

Edited by moderator Saturday, July 14, 2012 12:19:47 AM(UTC)  | Reason: Not specified

Warwick Wood  
#8 Posted : Tuesday, July 24, 2012 2:34:20 AM(UTC)
Warwick Wood
Rank: Administration

Reputation:

Groups: Registered, Administrators
Posts: 498
Man
Location: Byron Bay

Was thanked: 19 time(s) in 19 post(s)

Further to this, one of our clients that had this problem reported that on a Windows 7 PC with Office 2010 the problem was fixed by applying the Office 2010 Service Pack 1.

Office 2010 without the service pack generally seems to work fine, so it is possible that some minor Office update caused the issue.  Therefore if you do have this issue please make sure you install all Office Service Packs.

Warwick

Similar Topics
10460 General ODBC Error (ESdat)
by mcook 3/13/2012 4:55:58 AM(UTC)
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.