<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><title>RE: Axiant/Powerhouse on Server2008R2 - ODBC handling</title><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Are you able to connect to the ODBC connection using MS Access as an eternal table? That’s the first test I do on Windows to see if the connection is good. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Here is an article that discusses this approach.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="http://www.mcpressonline.com/application-software/microsoft/microsoft-computing-accessing-iseries-data-with-odbc.html">http://www.mcpressonline.com/application-software/microsoft/microsoft-computing-accessing-iseries-data-with-odbc.html</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=FR style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=FR style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Charles Finley<o:p></o:p></span></p><p class=MsoNormal><span lang=FR style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>(619) 795-0720<o:p></o:p></span></p></div><p class=MsoNormal><span lang=FR style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> powerh-l-bounces+cfinley=xformix.com@lists.sowder.com [mailto:powerh-l-bounces+cfinley=xformix.com@lists.sowder.com] <b>On Behalf Of </b>Bob Deskin<br><b>Sent:</b> Friday, November 28, 2014 3:05 PM<br><b>To:</b> Robert Thwaites; powerh-l@lists.sowder.com<br><b>Subject:</b> RE: Axiant/Powerhouse on Server2008R2 - ODBC handling<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p style='margin-bottom:12.0pt'><span style='font-size:10.0pt'>Could this be a permissions issue? Something more subtle than simply a user creating a user DSN? I have no idea where you would look, but Windows has picked up more and more permission and security nuances over the years.<br><br>Is this a centralized database or a database local to his machine?<br><br>Bob Deskin<br>PowerHouse Consultant<br>UNICOM Global<br><a href="mailto:bob.deskin@unicomglobal.com">bob.deskin@unicomglobal.com</a><br>(973) 526-3856<br><br>This message (including any attachments) contains confidential information that is PRIVILEGED, CONFIDENTIAL and/or ATTORNEY WORK PRODUCT and is intended only for the individual(s) named herein. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this message in error, please notify the UNICOM Systems, Inc. Postmaster (<a href="mailto:postmaster@unicomsi.com">postmaster@unicomsi.com</a>) of the error immediately, do not read or use the email and any attachments in any manner, destroy all copies, and delete it from your system if the communication was sent via email. UNICOM Systems, Inc. (818) 838-0606 Fax: (818) 838-0776<br><br><br><br><br>-----Original Message-----<br>From: Robert Thwaites [<a href="mailto:robert.thwaites@sewardconsulting.com">mailto:robert.thwaites@sewardconsulting.com</a>]<br>Sent: Fri 11/28/2014 5:58 PM<br>To: Bob Deskin; <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br>Subject: RE: Axiant/Powerhouse on Server2008R2 - ODBC handling<br><br>I am not surprised you don't recall, since it has been more than 2 years<br>since we last talked. Back in February of 2012 I had a series of IBM PMR's<br>with you where I first indicated that we use System DSN's at our customer's<br>site to avoid the need to setup and maintain multiple User DSN's - one for<br>each end user.<br><br><br><br>On my development server, I had my developer create a User DSN for himself.<br>I then dropped the System one (visible to anyone on the box). When he ran<br>our application, it could no longer see the database.<br><br><br><br>Robert Thwaites<br><br>Seward Consulting<br><br>(780) 426-4876<br><br>Mobile (780) 231-0067<br><br> <<a href="mailto:robert.thwaites@sewardconsulting.com">mailto:robert.thwaites@sewardconsulting.com</a>><br><a href="mailto:robert.thwaites@sewardconsulting.com">robert.thwaites@sewardconsulting.com</a><br><br><br><br>From: Bob Deskin [<a href="mailto:bob.deskin@unicomglobal.com">mailto:bob.deskin@unicomglobal.com</a>]<br>Sent: Friday, November 28, 2014 3:25 PM<br>To: Robert Thwaites; <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br>Subject: RE: Axiant/Powerhouse on Server2008R2 - ODBC handling<br><br><br><br>I'm using a User DSN for SQL Server. My user is an Administrator. I've<br>never heard of the type of DSN being stored but I'm not an expert on all the<br>internals. A user DSN should be visible to the user who created it on the<br>machine where it was created.<br><br><br><br>Bob<br><br><br><br>Bob Deskin<br><br>PowerHouse Consultant<br><br>UNICOM Global<br><br><a href="mailto:bob.deskin@unicomglobal.com">bob.deskin@unicomglobal.com</a><br><br>(973) 526-3856<br><br><br><br>This message (including any attachments) contains confidential information<br>that is PRIVILEGED, CONFIDENTIAL and/or ATTORNEY WORK PRODUCT and is<br>intended only for the individual(s) named herein. If you are not the<br>intended recipient, you are hereby notified that any dissemination,<br>distribution or copying of this email is strictly prohibited. If you have<br>received this message in error, please notify the UNICOM Systems, Inc.<br>Postmaster (<a href="mailto:postmaster@unicomsi.com">postmaster@unicomsi.com</a>) of the error immediately, do not read<br>or use the email and any attachments in any manner, destroy all copies, and<br>delete it from your system if the communication was sent via email. UNICOM<br>Systems, Inc. (818) 838-0606 Fax: (818) 838-0776<br><br><br><br>From: <a href="mailto:powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com">powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com</a><br>[<a href="mailto:powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com">mailto:powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com</a>] On<br>Behalf Of Robert Thwaites<br>Sent: Friday, November 28, 2014 5:11 PM<br>To: <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br>Subject: Axiant/Powerhouse on Server2008R2 - ODBC handling<br><br><br><br>Axiant/Powerhouse Handling for ODBC entries:<br>I recently tried changing from System DSN to User DSN and once I removed the<br>obsoleted System DSN I ended up with programs not seeing the database.<br>Do the compiled programs end up containing an indication of which type of<br>DSN is being used?<br>The dictionary itself doesn't appear to provide any syntax for picking what<br>type of DSN is being used, it just contains the name of the ODBC entry.<br><br><br><br>Robert Thwaites<br><br>Seward Consulting<br><br> <<a href="mailto:robert.thwaites@sewardconsulting.com">mailto:robert.thwaites@sewardconsulting.com</a>><br><a href="mailto:robert.thwaites@sewardconsulting.com">robert.thwaites@sewardconsulting.com</a><br><br><br><br>This e-mail message has been scanned and cleared by Postini / Google Message<br>Security and the UNICOM Global security systems. This message is for the<br>named person's use only. If you receive this message in error, please delete<br>it and notify the sender.<br><br></span><o:p></o:p></p><pre>This e-mail message has been scanned and cleared by Postini / Google Message Security and the UNICOM Global security systems. This message is for the named person's use only. If you receive this message in error, please delete it and notify the sender. <o:p></o:p></pre><pre><o:p> </o:p></pre></div></body></html>