What concerns me most about this thread is that there appears to be a lack of understanding about maintaining a SQL Server and its files.
With the right backup strategy and database settings, transaction log file size can be kept to a minimum - one that is relevant for the volume of data being read/inserted/updated.
Add to this some capacity planning and you reduce the risk of getting into these situations.
Not to mention that having a two week gap between backups is a dangerous way to live. Even for development databases where the data is not considered critical, there should be some strategy in place to allow the mimicking of the production environment and the protection of the data.
Having fallen into this trap and seen the trouble and pain it can cause, I strongly recommend that those of you who have experienced this problem take some time to look in BOL at backup strategies to reduce the likelihood of this happening again.
Life without beer is no life at all
All beer is good, some beers are just better than others