[AccessD] What problems converting A2K3 mdb to A2K7? - AHA!

Yea Tina!  You ARE a hero!

And as someone that has been an "IT PERSON" for more years than I care
to divulge I can state that 99% of IT People think Access is a toy and
not worth their time so I can see how several of them would have not
seen what seemed obvious to you or they were scared to break it and
then they would be responsible to fix it.Have a look, see it's Access,
shrug your shoulders and scratch your head. At my current company I am
the only person in our company - outside of the users - that isn't
afraid to use Access for real work. So any problem the users have with
Access the Computer Support area will contact me to help with even
though I am no longer in the IT department.

Great job for fixing the problem and thanks for sharing it with us.

GK

On 9/7/07, Tina Norris Fields <tinanfields at torchlake.com> wrote:
> Hi All,
>
> Yesterday I went to see the database.  As we sat down the client said
> that they had tried taking it over to a machine running A2K3 and it had
> run perfectly, but on the machine using A2K7 the thing seemed to be
> missing stuff.
>
> Okay, launch the database.  The startup form has a search combo box and
> command buttons to allow all kinds of things: add a new record of some
> kind to the transaction table, edit the profile, stuff like that.
> Clicking the buttons produced no response.  I looked up above the main
> window, just under the ribbon, and there was a warning statement that
> Access had disabled something it couldn't be sure was safe.  I clicked
> the options button, which opened the security window, clicked the choice
> to enable the disabled feature - I think it was macros.  Voila, the
> database works as it was supposed to.
>
> Apparently, the command buttons call macros and the macro feature was
> disabled.  That's all that was wrong.  I was there three minutes.  She
> thinks I'm a genius because, she said, five IT people had failed to
> figure it out.  I find that a little hard to believe.  But, it certainly
> made me feel good.
>
> Tina
>
>
> Tina Norris Fields wrote:
> > Hi All,
> >
> > A client called with this story:  We had a functioning database
> > developed in A2K3.  We gave the data to an off-site developer who did
> > some redesign work.  While the database was away being reworked, we
> > upgraded in the office to A2K7.  The database now seems to be missing
> > some fields and is not really functional.
> >
> > My first impression (I have not looked at the database yet) is that the
> > difficulties probably are associated with the off-site rework rather
> > than the upgrade.  But, I thought I'd check out what to watch out for
> > when I do go look at the database.
> >
> > Thanks for any advice and information on A2K3-A2K7 issues.
> >
> > Tina
> >


-- 
Gary Kjos
garykjos at gmail.com