linking front end to back end

In the database I have, its split into front end screens and reports and
backend tables for data. Of course, this means the linked tables are
linked using the linked table wizard to the network drive mapping the server
is on.

since this database will be used by multiple people, it then means that each
user must have the same drive mapped to the same drive letter. The linked
table manager doesn't recognize UNC encoding.

The problem we run into is having so many shares available to various users
that we are running out of letters and getting everyone to use one drive is
difficult. To help that problem (and WAN traffic delays) we've opted to
run the database on a citrix server so users in multiple sites can access
the database. Once again, because of the linked tables we cannot publish
the mde file to the users desktop and instead we have to make the users log
into the citrix desktop then run the program.

I'm trying to find a "Better way". Any insight would be appreciated.

re: linking front end to back end

"jayjay" <jjf_71@notmail.com> wrote:
[color=blue]
>In the database I have, its split into front end screens and reports and
>backend tables for data. Of course, this means the linked tables are
>linked using the linked table wizard to the network drive mapping the server
>is on.
>
>since this database will be used by multiple people, it then means that each
>user must have the same drive mapped to the same drive letter. The linked
>table manager doesn't recognize UNC encoding.[/color]

From what I've read you link with UNC names by using the Linked Table Manager by
going to the network neighbourhood and navigating from there.

See Relink Access tables from code http://www.mvps.org/access/tables/tbl0009.htm for
sample code to do it programmatically.

[color=blue]
>To help that problem (and WAN traffic delays) we've opted to
>run the database on a citrix server so users in multiple sites can access
>the database. Once again, because of the linked tables we cannot publish
>the mde file to the users desktop and instead we have to make the users log
>into the citrix desktop then run the program.[/color]

I don't quite understand the problem. Or is it that Citrix faithfully remaps all
your local drive letters to the Citrix environment?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

re: linking front end to back end

"jayjay" <jjf_71@notmail.com> wrote in message
news:c1h2ka$1hov66$1@ID-87431.news.uni-berlin.de...[color=blue]
> In the database I have, its split into front end screens and reports and
> backend tables for data. Of course, this means the linked tables are
> linked using the linked table wizard to the network drive mapping the[/color]
server[color=blue]
> is on.
>
> since this database will be used by multiple people, it then means that[/color]
each[color=blue]
> user must have the same drive mapped to the same drive letter. The linked
> table manager doesn't recognize UNC encoding.
>
> The problem we run into is having so many shares available to various[/color]
users[color=blue]
> that we are running out of letters and getting everyone to use one drive[/color]
is[color=blue]
> difficult. To help that problem (and WAN traffic delays) we've opted to
> run the database on a citrix server so users in multiple sites can access
> the database. Once again, because of the linked tables we cannot publish
> the mde file to the users desktop and instead we have to make the users[/color]
log[color=blue]
> into the citrix desktop then run the program.
>
> I'm trying to find a "Better way". Any insight would be appreciated.[/color]

Using a common mapped drive is a good idea in my book (perhaps you should be
using more sub-folder under a drive and not creating new drives for
everything??).

You can write some very simple code to allow the user to select the location
of your data file and then refresh the link information for the tables. Some
of our routines even allow the user to select what backend they are linking
to (Access, MSSQL via ODBC, etc) and just builds the linked table's
connection string.
--
Bradley
Software Developer www.hrsystems.com.au
A Christian Response www.pastornet.net.au/response