Hi Mickey,
If you aren't opposed to creating another table in your app, you could grab data from the jobs table to create Calendar Entries for them. This table could serve dual purpose of also storing your sub jobs data when you need to create sub-jobs.
In this way you can use the native parent-child relationship for your jobs and sub-jobs and have all of the data you need in one table to build the calendar and you can display the sub-jobs in an embedded report (perhaps a calendar?) on your job form.
I would then use Mark's suggestion to color code the "calendar entries" and "sub-jobs" to easily distinguish them on your calendar reports.
Also, keep in mind that you can use formula fields to generate custom strings to display on your calendars.
Jeff Richey | Solutions Consultant | Quandary Consulting Group
Website | LinkedIn | Knowledge Base