[AccessD] ODBC linked views fail in Access 2010

 > An aside: If your address is infact 5.123.456.789 that's your problem. ;-)

LOL, uhhh no.

The interesting thing to me is that the linked tables work just fine, even through whatever the 
application is going through to get out of the machine.  Only links to sql server views fail in this 
manner.

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it

On 2/5/2012 1:21 PM, Jim Lawrence wrote:
> Hi John:
>
> If I did not know better it sounds like the application via MS is making
> assumptions. It is saying that the address must be local; either in the
> 10.xxx.xxx.xxx or 198.xxx.xxx.xxx. You may have to set it up as UNC type
> address like \\5.xxx.xxx.xxx (In some programs, addresses like 5.xxx... are
> considered illegal being outside the standard address bandwidth.)
>
> The only reason that the 5.xxx... series of addresses are not challenged by
> the system is that they are managed at both the source and destination ends
> by Hamachi. New routers can stop Hamachi dead as they block all ports and
> addresses and only allow connection via addresses/ports/protocol types and
> even subnets, specifically entered into the allow list. LogMeIn has a core
> of Hamachi but they can proxy the addresses through port 80 if the required.
>
> In the long run maybe you should look at such solutions as OpenVPN
> (http://openvpn.net/), which has equal level of encryption, better security
> and a greater range of flexibilty. (Also the pricing is favourable for your
> type of project.)
>
> An aside: If your address is infact 5.123.456.789 that's your problem. ;-)
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Saturday, February 04, 2012 4:02 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] ODBC linked views fail in Access 2010
>
> My Access FE used ODBC links to tables and views in sql server over Hamachi.
> The FE is hitting a
> virtual machine on my network running Windows 7 X64 and SQL Server 2008
> server.
>
> The virtual machine is a member of a Hamachi network with an IP address like
> 5.123.456.789, and when
> I link to the tables and views I do so linking to the SQL Server instance
> using that IP address.
>
> I have been developing on another virtual machine in Office 2003.  The
> client has Office 2010.  One
> immediate problem is that I set the hidden attribute for every object such
> as forms and tables so
> that, when the FE opens, there is very little to see for the user to get
> into.
>
> The problem is that I cannot for the life of me discover where (in 2010) I
> go to check these boxes
> to allow me to see the hidden objects.  Worse still, I cannot even see the
> unhidden objects.  This
> appears to be mostly a case of Microsoft getting rid of the "database
> window" and doing everything
> they can to obfuscate how to get at the stuff that used to be readily
> visible in the database
> window.  And so I simply cannot even see any of the stuff I hid.   NOT my
> intention!  ;)
>
> The bigger problem is that all the views in the database under 2010 *can* be
> "seen", as can the
> tables.  I can double click to open the tables and see and edit the data but
> when I try and do so
> with the views, I get an error something to the effect that the ODBC
> connection to
> 10.5.123.456.789,1433 failed.  If you look closely, you will notice that
> Access appears to be adding
> a 10. in front of the valid 5. IP address, but only for the views.  Thus
> tables can be seen and
> opened, views cannot.
>
> I thought I would relink but Access is looking for the DSN of course which
> only exists on my main
> machine.  I am going to build on on the user's machine but I just thought
> I'd throw out there that
> this is happening and see if anyone had seen this bizarre behavior and if so
> have you discovered why
> it would be happening.  Specifically why the Access ODBC driver which is
> supposed to be connecting
> linked views suddenly adds a 10. in front of the otherwise valid IP address
> for the SQL Server.
>