Upgrading a databse to ms access 2007? Help

[cwoll]

Hi
I need help. I have a ms access 2003 database that I would like to
upgrade to ms access 2007. The first time I opened I had to fix a few
references it wanted a DAO2535.TLB file witch I gave it, and a
utility.mda file witch I think i gave it. The instructions on
Microsoft's web sight were not very clear where to put the utility.mda
so I am not sure if I have it at the right place. The Database does
not ask for it anymore.

I have tried to run it as a 2003 file and as a converted accdb file,
the problem is that I have a subform that is controlled by a query and
it only shows the first result instead of a list of results. The
strange part is when i start the program in the first few seconds it
show every thing but then the list disappears and only the first one
shows up. It all works fine with access 2003.

There are a bunch of other small bugs. It seam like it is slow to
refresh when switching tabs.

Am I wasting my time trying to make this thing work?
Is there some setting that I just don't have right?
Should I keep it as a mdb file or as a accdb?
Can any one help me?

This is just my hobby and right now I am frustrated!

Thanks
Clarence Wollman

[OldPro]

On Nov 1, 3:29 pm, cwoll <clarencewoll.. [e-mail] e:

Hi
I need help. I have a ms access 2003 database that I would like to
upgrade to ms access 2007. The first time I opened I had to fix a few
references it wanted a DAO2535.TLB file witch I gave it, and a
utility.mda file witch I think i gave it. The instructions on
Microsoft's web sight were not very clear where to put the utility.mda
so I am not sure if I have it at the right place. The Database does
not ask for it anymore.

I have tried to run it as a 2003 file and as a converted accdb file,
the problem is that I have a subform that is controlled by a query and
it only shows the first result instead of a list of results. The
strange part is when i start the program in the first few seconds it
show every thing but then the list disappears and only the first one
shows up. It all works fine with access 2003.

There are a bunch of other small bugs. It seam like it is slow to
refresh when switching tabs.

Am I wasting my time trying to make this thing work?
Is there some setting that I just don't have right?
Should I keep it as a mdb file or as a accdb?
Can any one help me?

This is just my hobby and right now I am frustrated!

Thanks
Clarence Wollman

I empathize as I have also tried to upgrade. My bosses were skeptical
when I told them of the serious bugs in 2007. I am still under a
mandate to upgrade, and will have to do so with experimentation to
find out what works and what doesn't. It hasn't been out long enough
for the needed bug-fixes and work-arounds to be published.
As to your particular problem, you haven't given enough details to
provide a clue as to why it isn't working. What kind of form is it?
What kind of control displays the data? Is the form and or control
linked directly to a table or query? Or is the data manipulation
taking place through code? Did all of the indexes and other
relationships of the suspect table show up in the new database?
In your case, I would recommend dumbing down the form until it starts
working... that should give you a clue of where to look to find the
problem.

[cwoll]

On Nov 1, 3:22 pm, OldPro <rrossk...@sbcg lobal.netwrote:

On Nov 1, 3:29 pm, cwoll <clarencewoll.. [e-mail] e:

Hi
I need help. I have a ms access 2003 database that I would like to
upgrade to ms access 2007. The first time I opened I had to fix a few
references it wanted a DAO2535.TLB file witch I gave it, and a
utility.mda file witch I think i gave it. The instructions on
Microsoft's web sight were not very clear where to put the utility.mda
so I am not sure if I have it at the right place. The Database does
not ask for it anymore.

I have tried to run it as a 2003 file and as a converted accdb file,
the problem is that I have a subform that is controlled by a query and
it only shows the first result instead of a list of results. The
strange part is when i start the program in the first few seconds it
show every thing but then the list disappears and only the first one
shows up. It all works fine with access 2003.

There are a bunch of other small bugs. It seam like it is slow to
refresh when switching tabs.

Am I wasting my time trying to make this thing work?
Is there some setting that I just don't have right?
Should I keep it as a mdb file or as a accdb?
Can any one help me?

This is just my hobby and right now I am frustrated!

Thanks
Clarence Wollman

I empathize as I have also tried to upgrade. My bosses were skeptical
when I told them of the serious bugs in 2007. I am still under a
mandate to upgrade, and will have to do so with experimentation to
find out what works and what doesn't. It hasn't been out long enough
for the needed bug-fixes and work-arounds to be published.
As to your particular problem, you haven't given enough details to
provide a clue as to why it isn't working. What kind of form is it?
What kind of control displays the data? Is the form and or control
linked directly to a table or query? Or is the data manipulation
taking place through code? Did all of the indexes and other
relationships of the suspect table show up in the new database?
In your case, I would recommend dumbing down the form until it starts
working... that should give you a clue of where to look to find the
problem.

Yes that is part of my problem. There are so many things that don't
work right I don't know were to start. I am under pressur to make it
work in access 2007.

What I would really like is for someone to look at it and see what
they think.

All you input is appreciated!
Like I say I am not a Pro.
Clarence Wollman

[Tom van Stiphout]

On Thu, 01 Nov 2007 22:54:37 -0000, cwoll <cl************ *@gmail.com>
wrote:

If you want a professional to look at it, perhaps "Microsoft Solution
Provider" in your yellow pages is a good place to start.
DAO2535 is a very old library and should not be needed. Select DAO 3.6
and fix what does not compile (Code Window Debug Compile).
Same thing with Utility.mda. Unless you are one of the VERY few who
knows what that thing does, uncheck it and fix what is broke.

The choice of MDB or ACCDB should be made based on needed features. If
you just want (need?) to upgrade, stay with MDB. The last thing you
need is one more variable.
You know you can run A2003 files in A2007, right? I just question the
need to upgrade.

-Tom.

>On Nov 1, 3:22 pm, OldPro <rrossk...@sbcg lobal.netwrote:

>On Nov 1, 3:29 pm, cwoll <clarencewoll.. [e-mail] e:

Hi
I need help. I have a ms access 2003 database that I would like to
upgrade to ms access 2007. The first time I opened I had to fix a few
references it wanted a DAO2535.TLB file witch I gave it, and a
utility.mda file witch I think i gave it. The instructions on
Microsoft's web sight were not very clear where to put the utility.mda
so I am not sure if I have it at the right place. The Database does
not ask for it anymore.

I have tried to run it as a 2003 file and as a converted accdb file,
the problem is that I have a subform that is controlled by a query and
it only shows the first result instead of a list of results. The
strange part is when i start the program in the first few seconds it
show every thing but then the list disappears and only the first one
shows up. It all works fine with access 2003.

There are a bunch of other small bugs. It seam like it is slow to
refresh when switching tabs.

Am I wasting my time trying to make this thing work?
Is there some setting that I just don't have right?
Should I keep it as a mdb file or as a accdb?
Can any one help me?

This is just my hobby and right now I am frustrated!

Thanks
Clarence Wollman

I empathize as I have also tried to upgrade. My bosses were skeptical
when I told them of the serious bugs in 2007. I am still under a
mandate to upgrade, and will have to do so with experimentation to
find out what works and what doesn't. It hasn't been out long enough
for the needed bug-fixes and work-arounds to be published.
As to your particular problem, you haven't given enough details to
provide a clue as to why it isn't working. What kind of form is it?
What kind of control displays the data? Is the form and or control
linked directly to a table or query? Or is the data manipulation
taking place through code? Did all of the indexes and other
relationship s of the suspect table show up in the new database?
In your case, I would recommend dumbing down the form until it starts
working... that should give you a clue of where to look to find the
problem.

Yes that is part of my problem. There are so many things that don't
work right I don't know were to start. I am under pressur to make it
work in access 2007.

What I would really like is for someone to look at it and see what
they think.

All you input is appreciated!
Like I say I am not a Pro.
Clarence Wollman