2007, 2010 or 2013.

[Paul H]

I've taken one step backward from Version 2010. 2007 is different in some practical ways that are frustrating me.

One would be, where is the Linked Table Manager. I've looked back and forth on the External Data ribbon and I can't find it. That's one.

Two is how the expression builder is reacting. In 2010, at least I would type in an "f" and i'd get a list of object beginning with "f", like Forms. It would let me build my expression very quickly using exclamation points and letting me pick from the list. Rather than get frustrated, can you just tell me whether this feature exists in 2007?

What other joys will I discover like where they hide the database options window (I found it). They (my customer) want things upgraded to 2010 at least, but are considerinig 2013, which I want to avoid. I've used 2010 for 3 years now and am comfortable with it and can work faster with. In addition, I am supposed to train some people here, which will be kind of hard if I don't know how to use the software. So my preference is to get 2010 installed and go with it. I changed my topic after I started typing this. I am interested in items one and two, but really what I want to know is if 2010 is an acceptable choice.

[Xipooo]

2010 is hands down the best version of the 3 IMO.

No need to upgrade to 2013 unless you're business practices require it. 2007 was the spring board that lept to 2010. Similar to how Vista became Windows 7. It was an improvement and they really were trying, but it wasn't until the next generation that they got it right. 2013 seems like they're trying to re-invent things again by dropping a bunch of nice things that were in 2010 and earlier versions.

[Paul H]

Thank you for your opinion Xipooo(???), especially as it was the option I prefer and suspected was best for the reasons you mentioned. I'll leave the floor open for other opinions, but I'm going to lobby for 2010.

[June7]

This may be a negative for Access 2010, unfortunately I haven't gotten a computer with 2007 still on so it I can go back and test. https://www.accessforums.net/forms/s...tab-41132.html

I seem to remember having to change some VBA code in 2010 related to a recordset (or was that the jump from 2003 to 2007, so maybe irrelevant).

Overall, 2010 is a positive upgrade. I don't want anything to do with 2013. 2013 is a drive toward the 'cloud' and web databases. It dropped some features that I never used but others have expressed dissatisfaction over (Collect Data, Pivot Chart/Table) but also drops support for DBF files so I converted legacy DBF tables to Access tables, just in case we are forced into 2013. Excel 2007 already cut support for DBF (will open but not edit nor save as).

[Paul H]

Thanks June,

Fortunately these applications are light on VBA and they are for sure shooting for 2010, which is good for me since that is where all my recent experience has been.

Paul