Migrating from Access 2000 to 2003 - new features? 3

[Blackshark]

Hello all,

The business I work for is migrating to Office 2003 next year from 2000. I was wondering if any Access 03 developers could point out any new features I should look in to, to improve my systems as I migrate them. I have tried to find 'whats new in 2003' etc... but would appreciate any other developers views.

The systems I write import csv files, show an image on screen that relates to each data row, after correction by the user, the data is stored in a seperate table and reports are run off this. I use PDF Pro Plus library to automate the production of the reports since 2000 does not support landscape and portrait reports in the same file (ie. snapshot). All the code is already written with ADO rather than DAO.


For the image view - I use the KODAK libraries which I know will need to be altered for moving to Win XP.

Thanks for you time

Tim

 

[THWatson]

Daniel
Thanks for your comments.

I think I should add that, in Access 2003, I was maintaining the default file system of Access 2000.

Tom

 

[RoyVidar]

How come then that of all the "Access 2003 errors" mentioned, the only "error" I've experienced, is that MS has broken the help files completely in the 2003 version?

Though I don't use it much, the Shell function works. Though I prefer using objects methods and properties of the Scripting Runtime, other methods of IO does work. Late binding definately also works. What little I use wizards, they also work. Yes, I've had crashes in 2003 too, but as in the previous versions, only in development, not in production. On my setups, 2003 is among the more stable versions, while 2002 was pretty bad. The 2000 version with SP's actually also became quite stable.

I think the .Recordset property of combos and lists became available in the 2002 version.

I think both of you (TWatson and danvlas) must have something pretty strange going on with your setups.

I think I've mentioned a couple of times here, that it seems the 2003 version might be a little less forgiving on subform/subreport references, but I use correct syntax, so I don't experience this, here's a sample

Access 2000, I think, would allow

[tt]Reports!rptMyRpt!rptMySubrpt.HasData[/tt]

While 2003 often will require proper referencing

[tt]Reports!rptMyRpt!rptMySubrpt.Report.HasData[/tt]

But, I'd say that's more a fail in the previous versions, not 2003 ;-)

Roy-Vidar

 

[THWatson]

Roy-Vidar
Although you may be right in suggesting that I have something pretty strange going on in my set-up, I can't for the life of me figure out what it might be. If I could that would be a huge bonus.
Using Access 2000, my databases work perfectly on several different computers.

I have the normal run of forms with option groups, some subforms, and the usual run of VBA code behind command buttons. I also have the normal run of reports, some of which have subreports. I have 2 or 3 modules that undertake specific actions.

In Access 2003, I run a normal form, or report, that has nothing in particular happening behind it, and boom, crash, "Microsoft Access has had to close. Do you wish to send an error report to Microsoft?" It then goes through the process of creating a backup...but the backup crashes when it is opened, and the original file can't be opened anymore.
I could live with a program crashing out. I can't live with the program trashing the database.

I know about using the proper syntax for subforms and subreports, and the HasData property, so the problem doesn't lie there.

Initially, when I encountered the difficulty with Access 2003 it was prior to Offices 2003 Service packs 1 and 2. Also I thought perhaps the laptop, upon which I was trying the program, didn't have sufficient memory (256 meg). But now I have a new laptop with 512 meg, and when I installed Office 2003 on it I also added the service packs.

It's a puzzle, to be sure...but also a very unhappy experience.

Tom

 

[THWatson]

Roy-Vidar
Just a thought...and an offer you, obviously, can refuse...I would be willing to send you a database that kept crashing, and you could see if it crashed when you tried to work with it in 2003. And if you could sense why it crashed that would be a huge bonus.

Tom

 

[ZmrAbdulla]

Tom,
Too many questions....
Did you ever try compiling the db?
Do you have any activex inserted in your forms/reports?
Do you Compact & Repair frequently?
Did you try importing all the objects to a new db with all the referenes added?
Did you try to find out when exactly it goes wrong? Particularly when you do a certain process and making sure the particular code have no syntax error.
Do you have proper error handling ?

________________________________________________________
Zameer Abdulla
Help to find Missing people
Even a thief takes ten years to learn his trade.

 

[RoyVidar]

Quite interesting, THWatson, though exchanging e-mail addresse here isn't exactly encouraged;-)

It does seem, however, that in this thread

http://groups.google.com/group/comp.databases.ms-access/browse_thread/thread/78aa08bde3c7298d

in CDMA, someone with a remarkably similar handle has a reply, and I think also with a nearly valid e-mail address ;-)

Roy-Vidar

 

[ZmrAbdulla]

Roy, are you sure you are referring to the correct thread in CDMA?

________________________________________________________
Zameer Abdulla
Help to find Missing people
Even a thief takes ten years to learn his trade.

 

[THWatson]

Zameer
There can never be too many questions. To answer the few that you have listed...

1. Yes, the database is compiled.

2. No, there is no activeX in forms/reports.

3. The database is set to compact upon close. Interestingly enough, when Access 2003 crashes, it goes through a compact and repair process before creating the backup... which is wonderful except when you try to open the backup it crashes and makes another backup...and one the series goes.

4. No, I have not tried to import the objects to a new database.

5. The database crashes in 2 instances: when opening a form, and when trying to run a report. There is no syntax error in the code.

6. Yes, error handling is in place.

Tom

 

[THWatson]

Roy-Vidar
I'll take a look at the remarkably similar handle with the nearly valid e-mail address in that thread. Thanks.

I know that exchanging e-mail addresses on here isn't encouraged.

Tom

 

[ZmrAbdulla]

Do you have references checked that are not relevent or not required in this db?

when opening a form, and when trying to run a report.

Any corruption on that particular form/report or their controls?

________________________________________________________
Zameer Abdulla
Help to find Missing people
Even a thief takes ten years to learn his trade.

 

[THWatson]

Zameer
No irrelevant references, and no corruption that I can see. And everything works perfectly in Access 2000.

Tom

 

[ZmrAbdulla]

Quite interesting..

________________________________________________________
Zameer Abdulla
Help to find Missing people
Even a thief takes ten years to learn his trade.

 

[danvlas]

Some /decompile attempts?
If not, re-create the offending objects. That may help.

HTH


Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[RoyVidar]

After receiving and testing the db, I'm still convinced MS Access in it self is not the reasons for this

* bad/corrupt install
* bad/corrupt libraries
* remaining bad stuff from previous installs
* OS, network, hardware related stuff
* ...

cause there where no problems whatsoever opening and using this db.

That the db is completely unrecoverable after a crash, is also outside my experience. I've been fortunate enough to have been able to resolve all such corruptions the last years through the /decompile option. Then there's also the JetComp utility which is downloadable from the Microsoft pages somewhere (but I've never had any need to even try it).

Roy-Vidar

 

[THWatson]

I really appreciated the oportunity to send the database to Roy-Vidar for testing. And I am also pleased that the database ran with no problems whatsoever. That would seem to mean there are no problems with the database and its construction...and I mention again that the database has run perfectly, on several computers, with Access 2000.

Therefore, where lies the problem? Roy-Vidar points to 4 possibilities.
* bad/corrupt install
How does an bad/corrupt install occur on two separate computers, on occasions a year apart?

* bad/corrupt libraries
What would corrupt the libraries? And if the libraries are corrupt why does everything run so well in Access 2000?

* remaining bad stuff from previous installs
When I installed Office 2003, I used Microsoft's recommended approach of "upgrading from Office 2000" which keeps former settings. Perhaps total removal of Office 2000 and then complete install of Office 2003 is the better method.
In actual fact, I did a complete removal and new install when I installed Office 2003 on my former laptop, and that experience was unsuccessful.
So...two different install methods...the same result.

* OS, network, hardware related stuff
I am running Windows XP with Service Pack 2.
As regards network, I have a desktop and a laptop on a home network (but my friend in Seattle, for whom the database also crashed in Access 2003, has one computer) and runs the same operating system.
Don't know what hardware could be a problem

So there I am...still at a loss for understanding, and finding the whole thing incredibly frustrating.

Tom

 

[Blackshark]

Tom,

I would suggest the following:

1. Create a blank MDB in Access 2003 on your system
2. Save, Close and reopen

If it opens - then continue

3. Import just the tables from the Access 2000 database in question
4. Save, Close and reopen

Repeat after importing the modules next, macros, queries, 1 form, then the whole lot, then reports. You should also test at each stage, open a table, use the immediate window to test one of the functions, open a query .....

The above should be able to be done in an hour even with a big complicated database and you will know for certain each step of the way that the database is OK or that a particular object type has caused the problem.

If you find after importing the modules that you are having problems, you might have an error in one of the installed libraries that Access is linking to.


On that point - I am sure we have all had situations where programs are installed and dont work. Yet - reinstall Windows XP and the software in question - works like a dream.


Remember that Access 03 will use different libraries to Access 2000. I dont know why the install program would not overwrite these when reinstalling, but to ensure it does, do a custom install and select install all from disk (or run all from my computer). Then open Add Remove programs, select MS Office 2003 and click the change option, select Repair Office in the panel that appears.


My two penneth is spent

Regrads Tim

 

[THWatson]

Tim
Thanks for spending your two penneth.

When I get up my nerve, and have some time to experiment, I'll give that a run.
I say "when I get up my nerve" because twice bitten three times shy.

On the other hand, it never has made any sense to me that Access 2003 wouldn't run things properly. That's what has caused me to continue to pursue an answer.
My experimental polls have been 50-50. Roy-Vidar found things to run without problems. My Seattle friend found it crashed. Confusing.

Thanks to everybody for the most helpful suggestions. I will post back when I have experimented further.

Tom

 

[THWatson]

Sorry...I meant to apply some stars, so just now did it.

Tom

 

[jsteph]

Tom,
I couldn't see if this was directly answered prior, but as to the Shell and Open problems, if you leave the default Macro Security to Medium or High, these won't work.

Go to Tools/Macro/Security and set it to low and it those functions should work.
--Jim

 

[lameid]

THWatson,

You had the question of why you might have corruption on different computers installed at different times.

2 ideas come to mind. First the installation meda is corrupt. Off one bit somewhere and you'd be done. Try using different media. Secondly, you might have some virus lurking on you network corrupting your install. If guessing this second case, I would drop all the partitions, and reinstall. I would install AV software from a source independent your office and update it(grisoft offers a free for home users version as well as trial. I think F-Secure offers a trial version as well.). Finally get your computer back on the network.