Access 2002 vs. 2003

[Albert D.Kallal]

Albert, one other question: if 2002 and 2003 share the same file format,
then one assumes that a 2003 database in that shared format could be used
in 2002. But how does one know which 2003 features (such as themed
controls) are available in 2002 if a database developed in 2003 is used in
2002?

For the most part, it does not come into play. I suppose trying to turn on
themes in a2002 would cause a trappable error.

Further, in a multi version environment and a multi-user environment, I
would still deploy a mde file to each user. This thus assumes a split
database.....

I do speak about splitting in the following article on how to run ms-access
in a multi-user environment.

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

I should also note that even when I develop, or work on a clients database
in a2000 format (and they are using a2000), I STRONGLY recommend that you
decompile the mdb file BEFORE deploying to the clients machine..and then
re-compile on their machine (there is some compile binary differences...and
thus you need to still take MUCH care as to deploying on target computers).

 

[Albert D.Kallal]

2) If A2002 and A2003 share the same file format, and if the db is in that

file format, why would the users need the A2003 runtime? If they have
Access 2002 as part of Office Pro, wouldn't they be able to run the file
in the A2002/3 format?

because you can ONLY create a MDE file in with the version of ms-access that
you have.

So, a2002 can ONLY create a mde for 2002, and a2000 can only create a mde
for a2000.

Apparently, people have noted that a 2002, or 2003 mde will work with the
a2003 runtime system...(but, I have not verified this myself).

You don't *have* to use a mde with the runtime..but as general development
approach, you should always distribute a mde file to the end users.

 

[Tony Toews]

because you can ONLY create a MDE file in with the version of ms-access that
you have.

So, a2002 can ONLY create a mde for 2002, and a2000 can only create a mde
for a2000.

Someone, somewhere is selling a $15 utility which can do this. I
suspect they've managed to figure out the syscmds function all.

Apparently, people have noted that a 2002, or 2003 mde will work with the
a2003 runtime system...(but, I have not verified this myself).

As should an A2000 MDE.

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

 

[david epsom dot com dot au]

We are distributing an A2000 mde to A2003 installations.
It works well now, but it didn't seem to work at first.

Either we were just unlucky at first, (possible) or else
subsequent service packs have harmonised the A2000 and
A2003 PC's.

(david)

 

[david epsom dot com dot au]

Is a gross overstatement.

....It's possible that I just had an unrelated failure. it
stopped working for me when I installed the patch, and
it worked again when I repaired the registry entry.

Can you confirm that this works for you? (using any existing
table at the end of the string)

codedb.execute "select * into [Excel 8.0;DATABASE=c:\tmp.xls].[fred] from
myTable"

(david)

 

[Neil]

SQL Server 7 will install in parallel with SQL Server 2000 and 2005 on

the same system. (Note that I haven't done this personally but I've
read it works and I have great faith in the SQL Server team and MVPs
that this works as advertised. <smile>)

So my mentioning that SQL Server 7 doesn't support named instances is
misleading in our discussion.

OK, good to know. Thanks.

By he I meant the IT person not the project manager.

Yes, that's who I meant too. I'm sure he already knows he's an utter idiot.


N

 

[Neil]

OK, thanks.

A2002 can run an A2003 MDB. A2002 would have to recompile the MDB
first though. Or it might be in a partially compiled state.

Many people though only distribute MDEs to the users so the users
can't muck with things or take the MDB home as it is the intellectual
property of the corp.

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

 

[GH]

George,

Thanks for the additional information. Linked Excel versus exporting
or writing to Excel in general are not quite the same thing, so I guess
my projects are good for now. We build all kinds of Excel
spreadsheets, but we don't use linked Excel "tables" to do so. I also
appreciate the links to Microsoft's articles on the changes.

- GH

 

[GiveMeChocolate]

I have been asked about this at work. I'm a little confused. Some
places say that only linking to an excel spreadsheet causes the
problem, but elsewhere it says specially linked to a named range in an
spreadsheet.

My Access version is SP3, Version 10.6501.6626. I created an excel
spreadsheet with a named range, linked to it from Access 2002 (Access
2000 file format) and was able to update the information in the named
range no problem.

What am I missing I wonder?

Joel

 

[Douglas J Steele]

What you would appear to be missing is KB904018, as mentioned in the article
to which George pointed you.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

I have been asked about this at work. I'm a little confused. Some
places say that only linking to an excel spreadsheet causes the
problem, but elsewhere it says specially linked to a named range in an
spreadsheet.

My Access version is SP3, Version 10.6501.6626. I created an excel
spreadsheet with a named range, linked to it from Access 2002 (Access
2000 file format) and was able to update the information in the named
range no problem.

What am I missing I wonder?

Joel

 

[david epsom dot com dot au]

Thank you for posting this: I've been wondering if my
experience was atypical.

For my benefit, could you confirm what you are seeing
by looking in the registry (use Run, Regedit) at

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel

Originally, my PC showed the Win32 value
c:\windows\system32\MSexcl40.dll

Later, this was changed to
C:\program files\Office11\msaexp30.dll

(david)

I have been asked about this at work. I'm a little confused. Some
places say that only linking to an excel spreadsheet causes the
problem, but elsewhere it says specially linked to a named range in an
spreadsheet.

My Access version is SP3, Version 10.6501.6626. I created an excel
spreadsheet with a named range, linked to it from Access 2002 (Access
2000 file format) and was able to update the information in the named
range no problem.

What am I missing I wonder?

Joel

 

[George Nicholson]

From within Access, you changed the linked data and those changes were also
automatically reflected in the Excel file? AFAIK, that, and only that, is
what the "update" is supposed to disable.

Some places say that only linking to an excel spreadsheet causes the
problem, but elsewhere it says specially linked to a named range in an
spreadsheet.

I assume that the link-to-an-excel file element is all that matters, but I
don't know that for a fact. I believe that the "named range" references
you've seen (I've seen them too) were in "how-to" workarounds of a specific
problem (i.e., "...you used a named range..."), but the possible problems
users might run into are not limited to that.

HTH,
--
George Nicholson

Remove 'Junk' from return address.

I have been asked about this at work. I'm a little confused. Some
places say that only linking to an excel spreadsheet causes the
problem, but elsewhere it says specially linked to a named range in an
spreadsheet.

My Access version is SP3, Version 10.6501.6626. I created an excel
spreadsheet with a named range, linked to it from Access 2002 (Access
2000 file format) and was able to update the information in the named
range no problem.

What am I missing I wonder?

Joel