I have an application that has tons of code, forms, queries and linked tables
(to Oracle). It resides on a network and since there is no real heavy
processing this has been working our great.
The linked tables are refreshed depending on a combo box pick, however they
maintain the same names. That way, all the processes work off the same table
names.
One user, no problems. Works swell.
However, now I have 2 users....and more coming
AHHHH
So I have a number of options:
1) I can create new tables with a suffix of the logon initials and
a) Change all the code to address all the tables by variables
adding the logon initials
or
b) Can I use an ALIAS after the logon somehow to let the computer
think that the table names are still the same when in fact they are pointing
to the specific new tables with suffix?
2) I can create a copy of the application on each users machine, link the
access tables from the MASTER and link the Oracle tables from oracle.
Problem is code maintenance. Every time We change code we have to distribute
it correctly. Bummer.
3) I can create a copy of the application and link the programs, forms,
queries and access tables from the MASTER and link the Oracle tables from
oracle. This sounds reallllly bad to me, but I would be able to change code
in one place...if it would work at all.
4) ??
What is the best and what is the most efficient way to handle this. Of
course there is a major time crunch....
Keith Wilby - 22 Mar 2007 09:26 GMT
> 2) I can create a copy of the application on each users machine, link the
> access tables from the MASTER and link the Oracle tables from oracle.
> Problem is code maintenance. Every time We change code we have to
> distribute
> it correctly. Bummer.
This is the preferred option. Code maintenance needn't be a "bummer" since
you can copy your development FE to a public read-only folder from where
your users can copy it to their profile's temp folder. This can be done
automatically using a batch file. Here's an example:
ECHO OFF
DEL "%userprofile%\desktop\MyShortcut.lnk"
XCOPY "X:\MyPublicFolder\MyShortcut.lnk" "%userprofile%\desktop"
DEL "%temp%\MyFolder\*.*" /Q
RD "%temp%\MyFolder"
MKDIR "%temp%\MyFolder"
XCOPY "X:\MyPublicFolder\MyFE.mde" "%temp%\MyFolder" /I
START "MyFE" /MAX "C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE"
"%temp%\MyFolder\MyFE.mde"
The first 2 lines refresh the desktop shortcut. Lines 3 - 5 refresh the
local folder structure. The last 2 lines copy the FE to the local folder
and then launch it.
HTH - Keith.
www.keithwilby.com
Aaron Kempf - 02 May 2007 19:43 GMT
you should move to SQL Server and use Access Data Projects
ADP is about 100 times easier to deal with
> I have an application that has tons of code, forms, queries and linked tables
> (to Oracle). It resides on a network and since there is no real heavy
[quoted text clipped - 31 lines]
> What is the best and what is the most efficient way to handle this. Of
> course there is a major time crunch....
Aaron Kempf - 04 May 2007 20:51 GMT
multi-user linked tables is an oxymoron
move to SQL Server and Access Data Projects
> I have an application that has tons of code, forms, queries and linked tables
> (to Oracle). It resides on a network and since there is no real heavy
[quoted text clipped - 31 lines]
> What is the best and what is the most efficient way to handle this. Of
> course there is a major time crunch....
Keith Wilby - 08 May 2007 15:55 GMT
> moron
You got that right.