Replies

The library Hans posted is the same one I am using.

Carla

I have a database that does the same thing periodically about once per month. Users don’t want a higher number even though it is just an identifier even if it really does not matter. I have a form I use to reset the seed of the autonumber field to the next highest number in the series. I am not sure where the function came from I found it in an existing database somewhere and it was not credited to anyone.
Here is the function:
Public Function ChangeSeed(strTbl As String, strCol As String, lngSeed As Long) As Boolean
‘You must pass the following variables to this function.
‘strTbl = Table containing autonumber field
‘strCol = Name of the autonumber field
‘lngSeed = Long integer value you want to use for next AutoNumber.

Dim cnn As ADODB.Connection
Dim cat As New ADOX.Catalog
Dim col As ADOX.Column

‘Set connection and catalog to current database.
Set cnn = CurrentProject.Connection
cat.ActiveConnection = cnn

Set col = cat.Tables(strTbl).Columns(strCol)

col.Properties(“Seed”) = lngSeed
cat.Tables(strTbl).Columns.Refresh
If col.Properties(“Seed”) = lngSeed Then
ChangeSeed = True
Else
ChangeSeed = False
End If
Set col = Nothing
Set cat = Nothing
Set cnn = Nothing

End Function

Create a form with a text box called NewHighestNumber and add a command button with the following code on the click event:

If ChangeSeed(“Vessels”, “ID”, NewHighestNumber) Then
MsgBox “Done”
End If

Carla

If the successor task has any % complete the task has an actual start date and will not move dynamically.

Carla

If the finish date of a predecessor task is extended then the start date of successor tasks will move forward if the dependancy relationship is Finish to Start, or Start to Start. Exceptions would be if you have constraints applied to the successor tasks. You could look at the Constraint dates table or for the constraint icons in the indicators column. You should not need to manually type dates in the Start or Finish fields for any tasks in the task entry table. If you manually type dates in these fields Project will automatically apply constraints for you. The default constraint applied to all tasks is As Soon As Possible. This means as soon as possible honoring dependancy relationships and any non-working days applied to the Project base calendar, or from a resource calendar for an assigned resource. If you have constraints you do need you can return to the default As Soon As Possible and change the constraint date to NA. Project will not accept N/A.

Carla

If you want to move all uncompleted work to be rescheduled to start from the current date forward then go to Tools, Tracking, Update Project and reschedule all uncompleted work to start after the current date. Remember that when you type a date manually into Project it will interpret that to be close of business on that date. If you want the start of business on the current date you would enter ex. 8/22/06 8:00 AM.
Finish Varience does not look at Actual Finish it looks a the Finish date in the current project so if a task has an actual start and does not yet have an actual finish if the finish of the task has slipped from the baseline date that amount would show in Finish Variance.

Carla

Before you reinstall search the PC for a file named Global.mpt and delete all instances before reinstalling. I have seen this problem on reinstall. The location of the Global.mpt is set in the registry and sometimes if it is not located you get errors.

Carla

You might try a compact and repair, or opening the databases through a shortcut with a start in pointing to your System.mdw.

Carla

I like the tutorials at this site:

http://functionx.com/access/%5B/url%5D

Carla

Thank you for the additional information about “unforseen” complications. There have been more than a few unforseen complications migrating from Access to SQL Server backend databases. We are finding solutions with the help of the lounge and a lot of reasearch.

After a little more trial and error we have found it is the (MAX) designation that is not translating. I think the MAX is new for SQL Server 2005 and I have Access 2002. If you use varchar(MAX) or nvarchar(MAX) you get a text field in the Access front limited to 255 characters. If you use varchar(4000) or nvarchar(4000) the Access front shows a Memo datatype and you can enter up to 4000 characters.

Carla

OK, I have found a way to force it to allow more characters by using ntext as the SQL datatype. I am thinking this is a very inefficient datatype as I recall that this datatype is not stored with the table itself. Is there a better solution. I also noted in the Access interface the datatype changes to Memo.

Carla

Hi Alan,

Yes, that is what I eventually found and you are showing it in the same location. I had to do a bit of looking and I was not sure this was the correct fix, but is is working fine now and showing the correct icons. I also still have my color folders.

Carla

I have been using this for a while and really like it, however I inadvertantly changed the icon for a local copy of an Access Database and found it changed globally all the Access default icons , it did not effect the custom shortcut icons for Access databases. It did not let me change the icon back, this just produced an error. I was able to “fix ” the icons back by locating on the Internet the Access key icon and copying and pasting the path to the icon I created with an icon converter from the image I found on the Internet in the browse section of the change icon dialog box, so users beware. I am sure there is a better way to associate icons to programs, but I don’t know how that functionallity works. I found the original path to the icon was to a executable file.

Carla

I have not seen this, but perhaps the multiple ghost tasks are showing up from multiple external links to the same task, anotherwords a ghost task is generated for each link? I was able to get what look like duplicate ghost tasks from creating concurently linked cross project tasks in the desktop version of Project. I was able to identify they were actually different tasks from different links by adding to the Task entry table the field named Project and the field named Unique ID.

Carla

Only downside I know of is after you link summary tasks to summary tasks you cannot create concurrency of summary task groupings from linking subtasks, you still have the option of Lag/Lead time for the link and that would create concurrency. I have been known to link summary tasks to summary tasks in consolidated projects when I am realtivley sure I will not need to overlap summary groupings and not had any negative consequences. Worst case scenario unlink the summary tasks and relink subtasks if necessary. I think that not linking summary tasks as a recommendation is valid, and is probably a good strategy particularly for inexperienced project users it makes the plan a little more flexible. My opinion on Project ” rules” is after you have some experience and can understand the cascading effects of changes you make and you have the ability to make changes without destroying the plan use what makes the picture that is most useful to you for decision making and communicating to others.

My opinion only,
Carla

Project still handles scheduling with the various calendars. You have to create a valid base calendar for the overall project, then use Project Base calendar as the base calendar for your resources. You can then define the appropriate schedule options using the resource calendar for each resource, this will accomadate any shift pattern. You also have the option to use a task calendar to schedule a particular task around a particular schedule. Calendars are dynamic in that if one of the elements of projects scheduling formula work = duration * units then one of th two remaining elements will recalculate. So if you make a change in resource schedules mid project then Project will make changes for you. Your challenge is to insure it makes the changes you want. Usually the biggest problem is users do not have a good understand of how project calculates and recalculates resource assignments and do not understand how the various calendars effectively.

I attended a seminar where I saw the 2007 version of Project a couple of months ago and did not see a lot of changes that would encourage me to spend the money for the new product. I saw the Office Suite changes that will offer the new menu and toolbar changes and I don’t think this was included in the new version of Project. The most interesting change I saw was they now have a feature that when you make an edit to the plan it will highlight everything that will change in the plan as a result of the edit. It is a nice feature for new users because one small change can affect the entire project plan. They have also made a lot of additions to the help features in an effort to help users understand how the product works.

One thing I would consider when purchasing is if you are planning on eventually using the Server based product for collaboration. The server based product does not work with Standard edition Project and requires I think at least the 2002 Professional version. I did not see a lot of what I would think to be significant changes to the standard product from 2000 to present. The addition of the task pane and some additional help features are about it.

Carla