ODBC Application

[Tom Deckert]

I am running an MS Access ODBC app on Terminal Server under MS Windows 2003
R2. It connects to a SQL Server 2005 DB. The app runs fine from the
console using the Access runtime engine, but fails when running from any
user logging in to the Terminal Server. The failure occurs when attempting
to access the SQL DB.

Any ideas?

TIA

 

[Jeff Pitsch]

Re: ODBC Application

Please forgive for the commentary but why do people still use Access as a
front end? It is completely limiting especially if you have to upgrade
office someday. VB or anything else is infinitely better.

But, did you install the runtime properly? what version of the runtime?
What is the error your receiving? What do the error logs say? Is your ODBC
setup properly? What account are you using at the console and the session?

Jeff Pitsch
Microsoft MVP - Terminal Services


"Tom Deckert" <tomd71@optonline.net> wrote in message
news:Xns9AE8B1128871Dtomd71optonlinenet@209.197.15.254...
>I am running an MS Access ODBC app on Terminal Server under MS Windows 2003
> R2. It connects to a SQL Server 2005 DB. The app runs fine from the
> console using the Access runtime engine, but fails when running from any
> user logging in to the Terminal Server. The failure occurs when
> attempting
> to access the SQL DB.
>
> Any ideas?
>
> TIA

 

[Hank Arnold (MVP)]

Re: ODBC Application

Because it's easy and VB is intimidating to many (myself included)...
Why is it limiting if Office is upgraded?

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services

Jeff Pitsch wrote:
> Please forgive for the commentary but why do people still use Access as a
> front end? It is completely limiting especially if you have to upgrade
> office someday. VB or anything else is infinitely better.

 

[Jeff Pitsch]

Re: ODBC Application

In my experience, Access is typically changed so much that upgrading it
becomes a problem. Unless you use extremely generic functions, etc
upgrading from 2003 to 2007 introduces incompatibilities. Also once you
open a 2003 access database with 2007, it upgrades the DB and te 2003 people
will be unable to access it. Now replace 2003 with any previous version and
2007 with any version above the previous and this is what happens.

You are artificially limiting yourself and hurting yourself and customers by
using Access. The worst thing we, as administrators, ever did was allow
access to be installed with Office. Ah if we could only go back in time to
the early days of Office

Jeff Pitsch
Microsoft MVP - Terminal Services


"Hank Arnold (MVP)" <rasilon@aol.com> wrote in message
news:e5golNJ8IHA.1196@TK2MSFTNGP05.phx.gbl...
> Because it's easy and VB is intimidating to many (myself included)... Why
> is it limiting if Office is upgraded?
>
> --
>
> Regards,
> Hank Arnold
> Microsoft MVP
> Windows Server - Directory Services
>
> Jeff Pitsch wrote:
>> Please forgive for the commentary but why do people still use Access as a
>> front end? It is completely limiting especially if you have to upgrade
>> office someday. VB or anything else is infinitely better.

 

[barret bonden]

Re: ODBC Application

Jeff, Access is just a wonderful environment for RAD; having VBA and a
form/query/report designer built in. I've written hundreds of apps in it -
from small ones for F500 firms to big ones for small companies. I don't like
the ribbon in 2007 but it upgrades OK; I've moved V2003 Apps up and down
with limited pain.



On another matter: On my TS test LAN, MS Access loads but does not run.
Server 2003 R2, Enterprise

Setup Terminal Server; licensing looks OK

Successfully installed MS Access 2003 on server. I can run it from the
Server box itself, and create new MDB's, etc.

From Remote Desktop I can run MS Access, but can not open and run existing
MDB's or create new ones No error messages - just nothing happens.









"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
news:eu$r66O8IHA.4140@TK2MSFTNGP02.phx.gbl...
> In my experience, Access is typically changed so much that upgrading it
> becomes a problem. Unless you use extremely generic functions, etc
> upgrading from 2003 to 2007 introduces incompatibilities. Also once you
> open a 2003 access database with 2007, it upgrades the DB and te 2003
> people will be unable to access it. Now replace 2003 with any previous
> version and 2007 with any version above the previous and this is what
> happens.
>
> You are artificially limiting yourself and hurting yourself and customers
> by using Access. The worst thing we, as administrators, ever did was
> allow access to be installed with Office. Ah if we could only go back in
> time to the early days of Office
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> "Hank Arnold (MVP)" <rasilon@aol.com> wrote in message
> news:e5golNJ8IHA.1196@TK2MSFTNGP05.phx.gbl...
>> Because it's easy and VB is intimidating to many (myself included)... Why
>> is it limiting if Office is upgraded?
>>
>> --
>>
>> Regards,
>> Hank Arnold
>> Microsoft MVP
>> Windows Server - Directory Services
>>
>> Jeff Pitsch wrote:
>>> Please forgive for the commentary but why do people still use Access as
>>> a front end? It is completely limiting especially if you have to
>>> upgrade office someday. VB or anything else is infinitely better.
>
>

 

[Vera Noest [MVP]]

Re: ODBC Application

First praise Access, and then post your problem with it.... I think
you have just made Jeff's point

Anyway, did you put the Terminal Server in install mode before you
installed Access? And then started the application once, while
still in install mode?
Are there any warning or errors in the EventLog of the server?
Have you used Process Monitor to see what is happening when you try
to start Access in a remote session?

http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/p
rocessmonitor.mspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"barret bonden" <support@networks-cc.com> wrote on 01 aug 2008:

> Jeff, Access is just a wonderful environment for RAD; having
> VBA and a
> form/query/report designer built in. I've written hundreds of
> apps in it - from small ones for F500 firms to big ones for
> small companies. I don't like the ribbon in 2007 but it upgrades
> OK; I've moved V2003 Apps up and down with limited pain.
>
>
>
> On another matter: On my TS test LAN, MS Access loads but does
> not run.
> Server 2003 R2, Enterprise
>
> Setup Terminal Server; licensing looks OK
>
> Successfully installed MS Access 2003 on server. I can run it
> from the
> Server box itself, and create new MDB's, etc.
>
> From Remote Desktop I can run MS Access, but can not open and
> run existing
> MDB's or create new ones No error messages - just nothing
> happens.
>
> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
> news:eu$r66O8IHA.4140@TK2MSFTNGP02.phx.gbl...
>> In my experience, Access is typically changed so much that
>> upgrading it becomes a problem. Unless you use extremely
>> generic functions, etc upgrading from 2003 to 2007 introduces
>> incompatibilities. Also once you open a 2003 access database
>> with 2007, it upgrades the DB and te 2003 people will be unable
>> to access it. Now replace 2003 with any previous version and
>> 2007 with any version above the previous and this is what
>> happens.
>>
>> You are artificially limiting yourself and hurting yourself and
>> customers by using Access. The worst thing we, as
>> administrators, ever did was allow access to be installed with
>> Office. Ah if we could only go back in time to the early days
>> of Office
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>>
>> "Hank Arnold (MVP)" <rasilon@aol.com> wrote in message
>> news:e5golNJ8IHA.1196@TK2MSFTNGP05.phx.gbl...
>>> Because it's easy and VB is intimidating to many (myself
>>> included)... Why is it limiting if Office is upgraded?
>>>
>>> --
>>>
>>> Regards,
>>> Hank Arnold
>>> Microsoft MVP
>>> Windows Server - Directory Services
>>>
>>> Jeff Pitsch wrote:
>>>> Please forgive for the commentary but why do people still use
>>>> Access as a front end? It is completely limiting especially
>>>> if you have to upgrade office someday. VB or anything else
>>>> is infinitely better.

 

[bliddel]

Re: ODBC Application

"Vera Noest [MVP]" wrote:
> First praise Access, and then post your problem with it.... I think
> you have just made Jeff's point
>
> >>> Jeff Pitsch wrote:
> >>>> Please forgive for the commentary but why do people still use
> >>>> Access as a front end? It is completely limiting especially
> >>>> if you have to upgrade office someday. VB or anything else
> >>>> is infinitely better.

I see the thread has been hijacked, and Tom has not gotten much help with is
problem, but I can share reasons why I still use Access as a front end.

First of all, I have five years practical experience using MS Access, and
none or virtually none with Oracle or SQL server, PHP, dot-net, C#, Java, etc.

Second, I can in a couple days throw together an entirely new report from a
proprietary Oracle database and a table outside the database which I created,
which presents dynamic images (detail) from left to right and top to bottom
(normalized in size) in landscape, based on three selected fields on a user
friendly form (combo boxes populated by queries of their own). Or, I could
instead spend 3-5 years and tens of thousands of dollars learning all sorts
of new languages and would still need a lot of help to do this same report
some other (theoretically better) way.

So what if Access is far from perfect and there are an overwhelming number
of "better" ways?

 

[Jeff Pitsch]

Re: ODBC Application

Well he hasn't exactly answered any questions now has he.


"bliddel" <bliddel@discussions.microsoft.com> wrote in message
news:6B5B5A7B-F895-4623-9222-2AC9A267871E@microsoft.com...
> "Vera Noest [MVP]" wrote:
>> First praise Access, and then post your problem with it.... I think
>> you have just made Jeff's point
>>
>> >>> Jeff Pitsch wrote:
>> >>>> Please forgive for the commentary but why do people still use
>> >>>> Access as a front end? It is completely limiting especially
>> >>>> if you have to upgrade office someday. VB or anything else
>> >>>> is infinitely better.
>
> I see the thread has been hijacked, and Tom has not gotten much help with
> is
> problem, but I can share reasons why I still use Access as a front end.
>
> First of all, I have five years practical experience using MS Access, and
> none or virtually none with Oracle or SQL server, PHP, dot-net, C#, Java,
> etc.
>
> Second, I can in a couple days throw together an entirely new report from
> a
> proprietary Oracle database and a table outside the database which I
> created,
> which presents dynamic images (detail) from left to right and top to
> bottom
> (normalized in size) in landscape, based on three selected fields on a
> user
> friendly form (combo boxes populated by queries of their own). Or, I
> could
> instead spend 3-5 years and tens of thousands of dollars learning all
> sorts
> of new languages and would still need a lot of help to do this same report
> some other (theoretically better) way.
>
> So what if Access is far from perfect and there are an overwhelming number
> of "better" ways?