New Vs Old Tables?

[alr0]

Hi All,

We have 100s of tables that are in Access 2k and we upgraded to Access 03 a few months ago. We are continuing to produce new mailing records in 2k tables and append them to master files.

While I see some new properties in 02-03 tables, I could not find a description of all of the differences to decide in which version we should produce new tables.

Does anyone know of a good comparison of features and compatibility issues or failing that some peoples experience making the transition?

Thanks,

alr

_____________________________________
If a large part of intelligence is the ability to generalize, it is ironic that a large part of what we call wisdom is the ability not to generalize.

 

[lupins46]

Here is a list of the main differences in table design features that affect developers moving from Access2K to Access2003.

1: option to propogate field property changes
2: .....er...(AFAIK) that's it....

 

[willir]

Not from the technical end, but from the "deployment" end, Access 03 is more restrictive. Licensing, using multiple versions of Access, run-time licensing restrictions have resulted in our "shop" not upgrading.

Richard

 

[lupins46]

Richard

Can you expand on this - I don't perceive there to be any differences at all in these areas.

 

[alr0]

Well...

The only important differences for my work from Office 97 to Office 03 are:

1) It crashes more
2) It is slower
3) I spend more time on supporting users
4) Files are not compatible

Now, after all users have been upgraded we are addressing the issue: in what format should our data be stored? It is important that we be able to open and work with data from other sources, whatever is being used.

My answer is that they should have dealt with this during the "evaluation process" but saying things like that just makes one unpopular.

Since everyone has 03 I don't expect any compatibility issues but is there any advantage to switching. Will the conversion cost even more in several years when we are forced for some unforeseen reason? It probably will make very little difference but I am stumped, irritated, and hiding my true reaction. Any thoughts?

alr

_____________________________________
If a large part of intelligence is the ability to generalize, it is ironic that a large part of what we call wisdom is the ability not to generalize.

 

[alr0]

Richard,

Are you running some Office 03 with Access 2k tables or have you avoiced 03 altogether?

alr

_____________________________________
If a large part of intelligence is the ability to generalize, it is ironic that a large part of what we call wisdom is the ability not to generalize.

 

[willir]

Sorry about the delay in getting back to those who wondered about my comments.

I do not have Access 2003 to "play with" at present, perhaps at the end of the week, but here is what "we" ran into...

- Unable to install Office 2003 into a different location than Office XP. Only able to install one version now, not run two concurrent versions.
- When Office 2003 was installed (upgraded), various third party applications failed to load Office app from within the third party app. For example, launching Excel from the 3rd party app -- works with Office XP and 2K, but not with 2003. Sorry can not share the name of 3rd party app -- confidential stuff. Uninstalled Office 2003 and reinstalled Office XP, file association worked as it should.
- Microsoft now requires verification for updates at their site for legit software -- not an issue with us who use a legit / licensed copy but I know some with legit copies are having problems with getting updates. I have read some "chatter" on this issue, but do not have time to provide supporting evidence at this time.
- Used to be able to create MDE run time database with Access for Royalty free distribution. Have not tried it with 2003, but literature suggests you know have to buy the developer's kit or like. Again, I read about this, but have other things to do before researching again.

And I use Access 2000 and XP front end and back end databases -- meaning Office XP front end accessing Access 2k backend; Office 2k front end accessing 2k backend; Office XP front end accessing XP backend. None of the locations I support have decided to upgrade to Office 2003 yet until the bugs have been worked out.

As per ALR comment on performance -- have you disabled AutoCorrect? From the menu, "Tools" -> "Options" -> "General" tab.

 

[lupins46]

- 'Unable to install Office 2003 into a different location than Office XP'
I can't really follow this since both OfficeXp and Office2003 install to their separate own folders and do not require any user action at installation stage to make this happen.


- 'Used to be able to create MDE run time database with Access for Royalty free distribution. Have not tried it with 2003, but literature suggests you know have to buy the developer's kit or like. Again, I read about this, but have other things to do before researching again.'

Absolutely not true. MDE has nothing to do with Access runtime distribution. It has ALWAYS been necessary to buy the developer tools to create a runtime distribution for an Access application.