Re: 2000/2003 Reference Problems

I feel better now, knowing that our management is not that much crazier than
some others. The scaries part is I work for one of the world's largest IT
providers!
Thank goodness there are no memo fields, so I don't have to face that.
Our users do not work with "live" data. Our accounting system is currently
Ross. As of Jan 1, 2006, we will be going to Lawson. Neither Ross or Lawson
will support the reporting and analysis we do of the data. Currently we
download an Access table that is prepared for us at another site. That table
is then parsed into the tables we need to do our reporting.
When we go to Lawson, which is on Oracle, we will have to do our own
downloads. This is where it gets goofy. Since the powers that be have
ordained that Access is an evil, unreliable, unclean application, we will not
be allowed to connect to Oracle vai Access. We will be required to dowload
using Crystal 9.0.
So, they are going to pay about $3,000 US to train me on Crystal so I can do
the downloads.
You raise an issue I was not considering. I don't currenly know Crystal,
but you said something about Excel. Are you saying that I will have to go
from Oracle to Crystal to Excel and then to Access. I hope I misunderstood.
That would make it even more stupid.
The interesting part is that Oralce will not know what is on the other side
of an ODBC connection. They will give us access to Oracle, but not allow
Acces to be used to do the download.

"vseale" wrote:

> So, the users are not using live data? In this case, you're being required
> to run the Crystal Report to download the data and import into Access? What
> version of Crystal will you be using? I seem to vaguely remember
> Crystal/Access having some form of link capability (probably thinking of
> something else; I can research tonight if you want). Hopefully, there are no
> memo fields; anything larger than 255 would preclude Excel as the
> intermediate file. Obviously, the human factor is making this more difficult
> than it need be. On a previous project, with our mgmt support pushing back
> we were able to get the Oracle folks to agree to ONE person being allowed to
> link to an Oracle query to export the needed data to our database (and she
> had to promise to keep her eyes closed when she ran it). This way it was a
> one-way process that in no way compromised security. Maybe they would be
> amenable (with your manager and two-levels ups support) to this type of
> compromise.
>
> "Klatuu" wrote:
>
> > Therein lies a big part of my problem. I work where Desktop Support is
> > responsible for imaging and configuring all computers. I have found that
> > they are not consistent in the way they do that. I have even found instances
> > where no Office libraries have been installed at all. Nothing I can do about
> > it. Oh, and Access is not a "supported product", so they will do nothing to
> > cooperate.
> >
> > Just to show you how silly they are around here, we are going to Lawson
> > which is on Oracle. That is where our data will be coming from, but we will
> > not update Lawson. I will not be allowed to connect to the Oracle database
> > to download my data. They are insisting I use Crystal Reports to download
> > the data into my Access application.
> >
> > Would you happen to know where a convenient bridge is?
> >
> > "vseale" wrote:
> >
> > > I'm in a similar situation with a 2000/2002 mixed environment and ran into
> > > the References issue. I'm using the 2000 and have some users with 2002. My
> > > workaround was to open a new database on a 2002 PC, set my references, save a
> > > copy to my PC and then export everything into 2002 creating a 2002 "master"
> > > using the 2000 format. I code in 2000, and export updates to the 2002
> > > master. The 2002 master can be opened on my PC so I can test it.
> > >
> > > I'm able to require all the users (small environment) to have the reference
> > > file locations standardized. That is a bigger issue in your environment.
> > > Without knowing the number of users have two potentially painful suggestions -
> > > 1) have the reference file locations copied/moved to the same path on the
> > > pertinent users PCs
> > > 2) identify the various paths of the files, copy the reference files on your
> > > PC to those folders and setup duplicate links
> > >
> > > Without a standardized environment, no easy solutions. Isn't reality fun!
> > >
> > > "Klatuu" wrote:
> > >
> > > > Thanks, Allen. I will do some testing. I had thought of that, in fact, but
> > > > had not really tried it because there are significant differences between the
> > > > reference library file locations and names between 2000 and 2003. If I use
> > > > this approach, will the machine that is still on 2000 keep its references or
> > > > will it try to find the 2003 references?
> > > > One other thing I had done to try to resovle this was changing all the
> > > > modules that are manipulating Excel from early to late binding, but that did
> > > > not resolve the problems.
> > > >
> > > > "Allen Browne" wrote:
> > > >
> > > > > Try decompiling the mdb using 2003 before giving the copy to the keeper.
> > > > >
> > > > > To decompile, enter something like this at the command prompt while Access
> > > > > is not running. It is all one line, and include the quotes:
> > > > > "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
> > > > > "c:\MyPath\MyDatabase.mdb"
> > > > > Then compact the database:
> > > > > Tools | Database Utilities | Compile.
> > > > >
> > > > > Access actually keeps 2 copies of each module:
> > > > > - the text version (what you read), and
> > > > > - the compiled version (the code that runs.)
> > > > > Each version of Access uses different binaries for the compiled version, and
> > > > > it is *very* common for Access to corrupt the mdb when it is trying to
> > > > > manage different versions.
> > > > >
> > > > > By decompiling in A2003 before you convert back, and then compacting the
> > > > > database, you are discarding the A2003 binary. A2000 will then create its
> > > > > own binary, and so the problem is solved. We have found it essential to do
> > > > > this every time a database has been opened in a later version, before trying
> > > > > to run it in an older version again.
> > > > >
> > > > > --
> > > > > Allen Browne - Microsoft MVP. Perth, Western Australia.
> > > > > Tips for Access users - http://allenbrowne.com/tips.html
> > > > > Reply to group, rather than allenbrowne at mvps dot org.
> > > > >
> > > > > "Klatuu" <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > news:7369B3EC-5D55-4AAF-A989-A2DCD0C4C865@xxxxxxxxxxxxxxxx
> > > > > >I am in a mixed environment. Some users have 2000, others have 2003. I
> > > > > >have
> > > > > > 2003 and do all the VBA coding. The Keeper of the DB is on 2000.
> > > > > > I am working with my mdb is 2000 format; however, my references are for
> > > > > > Office 20003.
> > > > > > I have tried exporting from my copy to the "Master" and I have tried the
> > > > > > Keeper importing from my copy to the "Master". In both cases, when the
> > > > > > Keeper opens the Master, it corrupts the database and we have to reload
> > > > > > from
> > > > > > backup.
> > > > > > The work around I have come up with is tedious. I copy all code to a
> > > > > > wordpad file and if it is from a form or report, I delete the code and set
> > > > > > the Has Module property to false. The Keeper then imports the objects and
> > > > > > pasts the code from the wordpad files into the appropriate objects and
> > > > > > compiles the database.
> > > > > > This avoids the corruption, but the must be a better way. Had I not
> > > > > > already
> > > > > > read all I can find on references and their problems, I would not be
> > > > > > posting.
> > > > > >
> > > > > > Thanks for any suggestions.
> > > > >
> > > > >
> > > > >
.

Relevant Pages

  • Re: 2000/2003 Reference Problems
    ... As of Jan 1, 2006, we will be going to Lawson. ... > download an Access table that is prepared for us at another site. ... > be allowed to connect to Oracle vai Access. ... >> Crystal/Access having some form of link capability (probably thinking of ...
    (microsoft.public.access.modulesdaovba)
  • Re: I cant find a SETUP.EXE in the SQL Plus Client ??
    ... someone else's server for testing some SELECT statements I'm ... free client because I don't own the Oracle license. ... SQL statements. ... There is no documentation with that download. ...
    (comp.databases.oracle.tools)
  • Re: I cant find a SETUP.EXE in the SQL Plus Client ??
    ... someone else's server for testing some SELECT statements I'm writing for them. ... How do I get a free Oracle client installed, if possible, so I can test some SQL statements. ... There is no documentation with that download. ...
    (comp.databases.oracle.tools)
  • Re: I cant find a SETUP.EXE in the SQL Plus Client ??
    ... someone else's server for testing some SELECT statements I'm writing ... How do I get a free Oracle ... client installed, if possible, so I can test some SQL statements. ... There is no documentation with that download. ...
    (comp.databases.oracle.tools)
  • Re: I cant find a SETUP.EXE in the SQL Plus Client ??
    ... someone else's server for testing some SELECT statements I'm writing for them. ... I just want a free client because I don't own the Oracle license. ... How do I get a free Oracle client installed, if possible, so I can test some SQL statements. ... There is no documentation with that download. ...
    (comp.databases.oracle.tools)