Re: Access 2: Can't Perform Join- Combined Fields Too Long

On Sun, 19 Feb 2006 13:47:40 +0100, "Arno R"
<arraNOcomSPAM@xxxxxxxxxx> wrote:

If you could zip me the database with *some data* that produce the error =
I would be willing to look at it.
I am still maintaining Access 2.0 databases, though for development I =
*only* use Acces97, Access 2000 and Access 2003 here.
I still think that Access 2.0 was/is a very good version. I assume the =
problems you describe will appear in any 'higher' version.
If you would send me the db I could test that also.

A colleague has tried to convert it into Access97 and it gives an
error message and won't open, even though it's working OK in Access 2.
I have Access2k (I think) on a laptop and could test it there.

BTW: I do not understand what you said concerning 'a fairly convoluted =
installation procedure on each PC'.

I work in an organisation that has literally hundreds of small
offices. In the area my Committee operates there are around 45
locations each with identically set up PC's running W2K. Some larger
locations have more than 1 PC, some many more. They are all on a WAN.

Access 2.0 was originally installed on the (then) PC's as part of
Office 4.3 (the version that included Word 6). When they upgraded all
the PC's they bought Office 97 but without Access. Office 97 is still
used on all these machines. Someone put together a self-extracting exe
with the Y2K fixed Access 2.0 and just dumped this file onto all the
machines, figuring I suppose that anyone who wanted to use Access
should be able to work out how to install it correctly. This file
(8.66mb including the Northwind and Solutions databases) has to be
placed into a dedicated directory and run to unpack the contents. Then
a file association needs to be set up. Then Access needs to be started
so that a MSACC20.ini file is created in the WINNT directory. Now the
file of the same name unzipped in the unpacking process needs to be
opened and its contents selected and copied, ensuring that the paths
specified in that file are correct, which they aren't because they
point to the former Office installation which was on Drive C (which on
these machines is completely locked down), so you have to change all
the paths you find. Next the MSACC20.ini in the WINNT directory needs
to be found using a search (the entire C drive is completely hidden on
these machines), and the contents of the clipboard pasted into this
file. At a pinch the messing about with MSACC20,ini can be omitted but
Access will then not be anywhere near fully functional.

I would call this a fairly convoluted install procedure. It's not
hard once you know how, and I now have the whole Access dir on a USB
drive so I can just copy it across and fix up the ini file and
association IF I am physically present, but I have my own job to do
and you try guiding someone who has trouble sending an e-mail through
the procedure above.

Some of the people in charge of these machines are not very computer
literate at all, and the procedure above is way too much to expect of
them.

As far as sending the database, I'll have to try to get the error to
occur again, perhaps in a query I create for this purpose. If I can do
that I'll forward it to you. I will have to trust you with the data in
it (which is actual Safety Committee minutes). Thanks for your offer.


fish

IME the Access 2.0 install is a breeze... For instance I can install the =
runtime with a 3 MB zip ...=20

Arno R


"Fish Womper" <fishwomper@xxxxxxxxxxxxxx> schreef in bericht =
news:43f8067e.21723765@xxxxxxxxxxxxxxxxxxxxxxxxxxx
On Sun, 19 Feb 2006 03:42:35 GMT, "Larry Linson"
<bouncer@xxxxxxxxxxxxx> wrote:
=20
"Fish Womper" <fishwomper@xxxxxxxxxxxxxx> wrote

My question to any Access 2 experts out there
is this: Is there any more elegant way to avoid
this error, which I fear will rear its head once
I'm relying on this thing to put out minutes,
agendas, etc.

I really don't know what "this error" is, much less the cause in your=20
database, so I couldn't answer this question. If you are encountering =
it=20
with test data adapted from real production, then you are right to =
fear that=20
it may occur in production, too.
=20
=20
The data I have entered is actual data going back the 8 months since
our Committee started. Once I put in the fourth month I got the error,
then got it working again by putting some of the report into
subreports each with their own query. After putting in the fifth month
and again the 6th month the error occurred again. Each time I added a
query to that underlying the main report, and this worked. The last
two months have gone in without the error.
=20
It seems like it's to do with the long text fields I am using, but
they aren't used in any joins, groups or sorts. They are the data I
want to return using combinations of meeting dates and issue numbers
to identify them.
=20
Nonetheless I'm still quite in awe of this almost 15 year old computer
program, which still today is an extremely useful tool.=20
=20
fish=20
=20
=20

Does this sort of error happen in later
versions of Access or only my
version?

I have never encountered the particular error you describe in any =
version of=20
Access.

I think you are going to have to dig in and dig around to try to find =
the=20
combination of things that are causing the error and then determine if =
they=20
can be fixed.

Unfortunately, Access 2.0 is long since "out of support," so you =
aren't=20
going to get any "live human help" from Microsoft on Access 2.0 =
issues. I=20
think someone claimed here that even some Knowledge Base entries and=20
articles on the Microsoft site dealing with Access 2.0 have been =
removed.

Larry Linson
Microsoft Access MVP




.

Relevant Pages

  • Re: Developer design Best Practices
    ... multiple smaller databases that were created adhoc on those servers for the ... SQL on these machines and than installed their application and pointed it ... production machines. ... Many of the objects in these databases are owned by not ...
    (microsoft.public.sqlserver.server)
  • Restore databases into a new installation of SQL Server
    ... I want to restore my databases from the old SQL Server installation ... Can anyone tell me how to restore my databases from the old SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Oracle RAC vs VM WARE
    ... virtual machines between the 2 new machines, with the databases ... I doubt though that 3 VMs, each with an Oracle instance running ... RAC may or may not be the right choice depending on ...
    (comp.databases.oracle.server)
  • Re: FreeBSD MySQL still WAY slower than Linux
    ... > yes random IO is more targetted to Databases. ... > noop, i have the installation always made in the same way, and i have respected ... certainly not the issue effecting database performance - for instance I ... find Postgresql consistently faster on RELENG_5 than on ...
    (freebsd-stable)
  • Re: MSDE and VS.NET Quickstart Tutorials
    ... databases (master, model, msdb, and tempdb). ... the 80\Tools\Binn directory of your installation. ... > SQL Server does not exist or access denied. ...
    (microsoft.public.sqlserver.msde)