Access 2010 & Visual Studio

Yes you can. You could do this in earlier versions of vs/vba as well. Treat it is an object like you do with Excel.
Here is an example of creating a database http://www.freevbcode.com/ShowCode.asp?ID=5797

What is it exactly you want to do?

I think some history about our company will help!  We are pretty much a data company.  We get a lot of data from our clients, format and transform it, and then make business decisions based upon the results (I guess that describes most companies, huh?).  One of our business units is run by a few old-school guys who are very resistant to change.  Even though all of our data is stored in SQL, these guys like to download specific data pieces into Access databases.  These databases have custom queries, forms, and macros to analyze and format data.  Currently, I have zero control migrating these guys to our enterprise system, but I am expected to maintain these DBs.

There is a "master" DB that contains the newest business logic, queries, etc.  This particular business unit downloads data into one of these shells and then performs whatever queries and macros necessary to manipulate and format the data.  Recently, they have requested many changes (small in scope).  These changes include, for example, including additional columns in queries or making a minor mathematical calculation changes.  We use TFS 2010 and Visual Studio 2010 Ultimate for all of our other development activities.  My hope was that I could source control this "master" DB, program changes to the DB in VS, and then use some sort of deployment method to release changes.

Although creating an Access DB as an object is one possibility, I'm lazy and don't have the time to support such an endeavour.  Writing code for everything just isn't within our budget and timeline.  I am used to creating Excel and Word documents, using the templates that VS provides, to create and edit functionality.  I was hoping something similar could be accomplished with Access!  On a side note, maybe I'm asking too much, since Access 2010 still doesn't support the bigint type... ;)

I'm with imnorie on this one: You could possibly manipulate some of the Objects, but overall if you must maintain a full Access database (Forms, REports, etc), then you'll have to do this directly in Access. If your current "old-school" guys are comfortable with Access, then I seriously doubt you'll get them to work with VS. It's a pretty big jump for most Access users (even if they're power users).

Apparently you can't use VS to create MS Access projects.