[AccessD] Office on a server - where did it go?

 > Why do you need to do decompile (just curious).

Decompile is a tool that, when you need it there is no substitute.  I am amazed that you have 
apparently never used it?  I just set up a decompile shortcut in every machine I do development, 
kind of as a standard thing.  There if I need it.  I cannot count the times that it has solved 
problems in the last 10 years.

 > Can you copy the FE to your machine, decompile, and replace?

The server at their office is "my machine" unless you mean my machine at my office, in which case 
yes I could but it is clumsy, and slow.

John W. Colby
www.ColbyConsulting.com


Rocky Smolin wrote:
> Why do you need to do decompile (just curious).
> 
> Can you copy the FE to your machine, decompile, and replace?
> 
> Rocky
>  
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: Tuesday, June 02, 2009 5:36 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Office on a server - where did it go?
> 
> One client has a server running Windows 2003 and SQL Server as a BE to
> various Access FEs.  I was brought back in to this client because the
> company that did the conversion from Access BE to SQL Server was not doing
> what they said they would do.  Anyway...
> 
> I use VPN and remote desktop to remote in to the server.  It is my dev
> machine simply because they do not have another machine to set me up on.
> 
> My problem is that they installed Office on this thing (I guess), or at
> least I can use office on this thing but I cannot FIND the actual office
> install.  In order to get a /decompile going I need to use a shortcut to the
> actual Access EXE and then use the /Decompile switch.  Or at least that is
> how I know to do it.
> 
> Since I cannot find the exe on the machine I am unable to do this.  Needless
> to say, Decompile is rather important.
> 
> I think what is going on is that the office was made part of a domain that
> exists at another office. 
>   As such I am guessing that my user is "virtual" or whatever you call it,
> and thus it can use office even though it is actually installed somewhere
> else, probably in that other office.
> 
> Has anyone ever run into this?
> 
> --
> John W. Colby
> www.ColbyConsulting.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>