To LINQ or not to LINQ

[cptHotkeys]

Hi, I am writing some software which is heavily dependent on a database, the coder who started the project and has since disappeared off face of the earth, he wrote part of the project using Silverlight, LINQ and the entity framework.

The database will need regular modification and additions of both tables and fields. New classes will be needed and existing classes will need modifications also, this will cascade through to the user interface, so all three tiers will need regular additions and modification. (This is required to meet new customers needs, industry standards and government legislation)

How well does LINQ and the Entity Framework suit this kind of scenario?
Am I better off doing the coding the old fashioned way, write my own classes for data access using SQL statement strings and create my own classes to represent the database objects and functionality (which i am more familiar with)?

My little understanding of LINQ and the Entity framework tell me that they are going to make updates, modifications and additions more cumbersome than if I done the work the old fashioned way, correct?
This is my first project that uses LINQ and Entity framework so my experience with maintenance is nil.