January 21, 2016 at 5:31 am
I've used MS Access before as a database in some applications I've written. But I've never learned how to write Access applications. In other words, for me it's only been Access as a database, never as an application.
I ask because I'm wondering how I put that succinctly in my resume? Saying something like "used MS Access as a database, but not having written any MS Access applications" is too long. Or would I be better off not listing MS Access at all?
Rod
January 21, 2016 at 6:27 am
Depends on what kind of position youre looking for. If youre getting calls for Access Programmer positions (eg Forms and Reports dev) and you are not interested in that then qualify it to say "as a data source". In general though it's fair to simply list "Access." Like Access, SQL Server has many subsystems and unless you want to specialize in one subsystem or rule out offers for other subsystems then no need to qualify it.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
January 23, 2016 at 8:37 am
Thank you, Orlando.
Rod
January 23, 2016 at 9:26 am
Nice approach, Orlando. The term "as a data source" is pretty succinct.
Dr. Who, my guess is that if you put SQL Server on your resume, the reader of the resume will understand that you know how relational databases work in general. Granted, this does assume some level of technical competency of the reader, which may or may not be a safe assumption. If the reader is the HR person filtering the stack of resume, you'd be out of luck. It's probably best to take Orlando's approach.
March 17, 2016 at 5:52 pm
The word that struck me would have been Data Repository, but Data Source is probably better. I always trend towards polysyllaby. 😀
Personally, I'd suggest dropping some coin on Microsoft's Access 2010 Inside Out, they have two volumes, one on VBA programming and one on the non-VBA aspects. Work 'em over, develop some apps of your own, even if it's just piddly stuff for your own use that no one else is likely to see.
As a suggestion, build a music library database. Tables: Artists, Albums, Tracks, Genres, Playlists. Build relationships, then start building forms and reports.
Just my $0.002 worth.
Hey -- if you're Dr. Who 2, then why is your photo of #4? 😛
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
March 17, 2016 at 6:43 pm
Or link to your SQL Server database and use linked tables etc... I wouldn't waste a lot of space on my resume on Access. The market for it is almost nil. If you can do SQL Server and C# or other .NET language, then you'd be in business.
March 19, 2016 at 8:35 am
pietlinden (3/17/2016)
Or link to your SQL Server database and use linked tables etc... I wouldn't waste a lot of space on my resume on Access. The market for it is almost nil. If you can do SQL Server and C# or other .NET language, then you'd be in business.
SQL Server and C# is really my forte. MS Access is only something I used as a data source.
Rod
March 19, 2016 at 8:56 am
Then honestly I'd leave it off. I don't think it's worth the space.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply