[AccessD] Access 2007 on a network

Jim Dettman jimdettman at verizon.net
Sat Aug 25 06:46:56 CDT 2012


> <<The VPN is into the network, and he's using it because it's the way the
> company laptops are set up to connect.  He doesn't have a desktop to remote
> into.  >>

That's most certainly why then; you can't run Jet over a WAN.

Jim
Sent from my iPhone

On Aug 24, 2012, at 10:39 PM, Charlotte Foust <charlotte.foust at gmail.com> wrote:

> I inadvertently misled you on the citrix. We have access to the citrix
> network for various things like software not installed on our machines,
> etc., but it isn't in play here.
> 
> The VPN is into the network, and he's using it because it's the way the
> company laptops are set up to connect.  He doesn't have a desktop to remote
> into.  We run lots of Access apps from the network, and it doesn't really
> make sense that he can't, but when he copied the FE to his virtual personal
> folder and ran it from there, it worked just fine.  That's the kind of
> network craziness that keeps me writing code and avoiding hardware!  The
> back end is on the same server as it was, and the FE has table links to the
> same folder the FE came from.  My head aches!!
> 
> Charlotte
> 
> On Fri, Aug 24, 2012 at 11:06 AM, Jim Dettman <jimdettman at verizon.net>wrote:
> 
>> <<It works fine, including Access apps, but the user
>> who is trying to VPN in is the one having issues (and causing them)>>
>> 
>> Is the app local on their station?  Why are they using a VPN?  Or is the
>> Citrix server only available internally?
>> 
>> Jim.
>> 
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com
>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
>> Sent: Friday, August 24, 2012 10:41 AM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] Access 2007 on a network
>> 
>> Thanks, but I have no control over the network setup, period.  We all log
>> into citrix and we all have a personal citrix drive, which is where our
>> desktops are located.  It works fine, including Access apps, but the user
>> who is trying to VPN in is the one having issues (and causing them)  I
>> can't duplicate the setup because I'm not assigned a company laptop.  And I
>> haven't done front-end updating because the app is still under
>> development.and I don't yet know how it's going to be deployed, but it will
>> probably be from a shortcut on their desktop.
>> 
>> Charlotte
>> 
>> On Fri, Aug 24, 2012 at 6:32 AM, Michael Mattys <
>> michael at mattysconsulting.com> wrote:
>> 
>>> Charlotte,
>>> 
>>> " I'm not about to build an elaborate front end updater ... "
>>> 
>>> Tony Toews relays this information which may be of help:
>>> 
>>> See http://www.granite.ab.ca/access/terminalserver.htm
>> 
>> 
>>> 
>>> 
>>> 
>>> " The solution was to update my Auto FE Updater to support
>>>  directory naming by userid so you can put individual FE
>>>  MDB/MDEs in their own directory."
>>> 
>>> Michael R Mattys
>>> Mattys Consulting, LLC
>>> www.mattysconsulting.com
>> 
>> 
>>> 
>>> 
>>> 
>>> 
>>> -----Original Message-----
>>> From: accessd-bounces at databaseadvisors.com
>>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
>> Foust
>>> Sent: Wednesday, August 22, 2012 9:45 PM
>>> To: Access Developers discussion and problem
>>> Subject: [AccessD] Access 2007 on a network
>>> 
>>> I've got a beta deployed on a citrix network.  Shared drive with
>> enterprise
>>> and I own the folder.  I'm getting reports of people not able to log in
>>> from
>>> elsehwere in our network.  And I'm seeing corruption as a result of their
>>> efforts. I use an mdb in 2002-2003 format.  I just want them to be able
>> to
>>> explore the thing, and I can't duplicate the issues from my machine going
>>> into the same shared folder and just running it.  IT doesn't support
>> Access
>>> and wouldn't know how to start.  All of use basically run off of citrix
>>> drives unless we specifically save stuff to C:  Our "desktop" in on a
>>> personal enterprise drive, so having them copy it there might not make
>> any
>>> difference; and anyway, I'd have to make sure they all got the latest
>> build
>>> every day!  I'm not about to build an elaborate front end updater for
>>> something that will evolve away from Access as some point, especially
>> when
>>> they still have nailed down all their requirements.
>>> 
>>> Any suggestions (keep it clean, please.  I'm a Buddhist)
>>> 
>>> Charlotte
>>> --
>>> AccessD mailing list
>>> AccessD at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/accessd
>> 
>> 
>>> 
>>> 
>>> Website: http://www.databaseadvisors.com
>> 
>> 
>>> 
>>> 
>>> 
>>> --
>>> AccessD mailing list
>>> AccessD at databaseadvisors.com
>>> http://databaseadvisors.com/mailman/listinfo/accessd
>> 
>> 
>>> 
>>> 
>>> Website: http://www.databaseadvisors.com
>> 
>> 
>>> 
>>> 
>>> 
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> 
>> 
>> Website: http://www.databaseadvisors.com
>> 
>> 
>> 
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> 
>> 
>> Website: http://www.databaseadvisors.com
>> 
>> 
>> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



More information about the AccessD mailing list