Users who wish to use a program developed in 2003 are now having to
purchase 2010. Will the 2003 program run on 2010 just as easily as it
does on 2007? Nancy

"Tomahawk Lady" <nancycmarshall (AT) verizon (DOT) net> wrote

For the most part, they run quite well.

If you attempting to Share the database in a folder, then you want to split
the database as Access don't take to well to allowing different versions
attempting to open + run the application at the same time.

As a goal, over time likely you want to covert the formats to accDB format,
but my experience is that Access 2003 applications run quite well in 2010.

The problem areas are if you using User level Security, then for 2010, you
have to use a shortcut that specifies the workgroup.


Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoSpam_kallal (AT) msn (DOT) com

Tomahawk Lady wrote:

In my very preliminary testing of 2010 running a 2000 MDE I found...

Lebans PDF output broken.

The "tabs" on TabControls do not display. They work if you click where they
should be, but they are not visible.

I expect to find more problems when I have more time for testing. Perhaps
some issues that affect a 2000 MDE would not affect a 2003 file, but that
remains to be seen.

particular the main form where you enter client data. Do we have any
idea whether Microsoft plans to fix this problem?

Rick Brandt <rickbrandt2 (AT) hotmail (DOT) com> wrote in
news:i2t0h3$nt2$1 (AT) news (DOT) eternal-september.org:

But not needed any longer, since PDF printing is included.

I have had tab control display issues in A2003 with themes on.

It shouldn't make a difference, but have you tried an MDB?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

"Tomahawk Lady" <nancycmarshall (AT) verizon (DOT) net> wrote

On my applications that I tested, my tabs displayed just fine. So, I am not
sure under what cases they don't work.
So, for my applications, I not had nor seen this problem (and I running with
themes on).

Of couse converting up to 2010 would fix this.

I think the best advice here is to test/try your applications before you
make any big commitment.

In my case, I had rather good luck.

So, my choice at the end of the day would be to suggest you convert those
access 2003 to 2010 applications,
but my experience has been quite good with testing/running existing 2003
applications in 2010.

However, if you must run a mix of 2003 users and 2010 users, then I would
suggest you split the database.
A split database allows one to reliably run Access applications with
different versions of office/access
which is the reality for many companies as they upgrade computers over time,
and not all at once.

Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoSpam_kallal (AT) msn (DOT) com

David W. Fenton wrote:

True, if every user is going to switch to 2007 and higher all at one time
(ain't gonna happen at my company).

We plan on going no higher than 2007 until everyone is at that level (since
2007 supports both Lebans tool and the native PDF). Once we have no one at
2003 or lower then I can switch to the native functionality. After THAT we
could dabble with some users going to 2010.

I plan on going to the "buttons" style or to "none" style with my own
controls for changing tab pages. Because you're correct the tabs have
looked like crap since 2003 came out.

At this point all I have done is download the MSDN subscription copy of
Office 2010 and spent about 10 minutes with my main app just to see what
would shake out. Heck, I'm still dealing with users coming across
functionality that 2007 has broken.

Rick Brandt wrote:

When you try using None for the buttons, be sure to watch
the cursor as you tab through the form. I don't have A2007
anymore, but, when I tried that in the past, the cursor went
to a nonexistent tab (ie. disappeared) before going to a
control on the tab.

--
Marsh

On Jul 30, 8:49*am, Rick Brandt <rickbran... (AT) hotmail (DOT) com> wrote:

Strange. I'm using this to generate pdfs and attach them to a message
in Outlook and it's still working fine under 2010.

Wayne wrote:

Well, in my test I got a PDF file, but the formatting was all messed up
compared to other versions.

Didn't we hear that A2010 got rid of Snapshot Format as an output option?
Doesn't Lebans' tool work by creating a snapshot and them embedding that
into a PDF? Based on that I was quite surprised to have gotten any output
at all. I was expecting an error message.