Project - Temp projects in Project Database

One of my users of the project database had a time out issue while trying to
save a file over the network.  Project then created a temp project,
AUDIT_PLAN_TEMP.  What do I do with that plan?  I want to eliminate the TEMP
project without destroying what was already there.  When I go into the
database with access, I see the tasks are still there for the original plan,
but when I open the original plan through project, there are only a few
tasks.

Is there some repair process I can use to get things back to proper state.
--
Yours Fictionally, Biggles

  Rod Gill replied...

There isn't a utility, but you can manipulate the database so you change the
project id for the old tasks. Of course make a copy of the .mdb file first!

Read the projdb.htm file carefully (it's in one  of Project's program
folders)

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

Problem with VBA Code for Massive Publish Project Hello: I have created a small VBA program for Project Professional 2007 in order to implement massive publishing automation tasks. The program Project task. The task list is written in the same MPP file that contains the VBA program. As the Project Professional session is already logged with Project Server, the VBA program simply loads each Gantt from the list on Project Professional, attempts to publish it an interactive process. . . which defeats a big part of the program functionality. Here follows the VBA code for Project Professional 2007: Sub Publicacion_Normal() ' Publicacion_Normal Dim Tarea As Task Dim Gantt As Armas Project Manager Project Developer Discussions Project Server (1) Project.QueuePublish (1) ActiveProject.Tasks (1) VBA (1) PjDoNotSave (1) FileOpenEx (1) TiempoPausa (1) FileClose (1) At the beginning of the code following. The Publish Method has two arguments and even though both arguments are optional, sometimes VBA wants to see a value for at least one of the arguments. In your code avail, sadly enough. The publishing window keeps popping up. Bypass alternative: is there anyway in VBA to tell the publishing window to click at the Publish button? Thanks in advance, Sebasti

Server (1) Microsoft Project (1) Project 2003 (1) Project 2007 (1) Office (1) Oracle (1) VBA (1) Hi, You can go three ways: 1) stand alone application using .net and using automation to control Project and send data 2) Use a VBA macro in Project (called from an external program using automation and the Macro method) 3 data to send to project, then the copying of data between programs is slow. Once VBA has all the data it needs it is actually very fast as it is all is easier and quicker to develop code in that C# as you can: * Copy working VBA code to VB easily * VB intellisnese is better * VB allows optional parameters, which given the and maintain. - - Rod Gill Microsoft MVP for Project Author of the only book on Project VBA, see: http: / / www.projectvbabook.com _ __ __ __ __ _ Information from ESET Smart Security, version of virus signature database 4659 (20091203) _ __ __ __ __ _ The message was checked by ESET Smart Security. http: / / www.eset.com regard to: 1). I thought that 'automation' was no longer possible in Project 2007? 2) VBA macros are probably not up to our needs. There is an enormous amount of VB an ed ally g an ot ters hat ng with Also it this g ture database 4659 (20091203) _ __ __ __ __ _ Proj07 works fine with automation. I use Proj07 with automation, controlling Gantt

Determining "nullness" of custom fields using VBA (not PSI) Project I have built a custom field editor addin in MS Project (using cache is not properly updated when writing back to the server - so reverted back to "VBA"-style code). I need to determine if a custom field (for example a cost) is in it. Using the PSI, this is easy to check, however using the client-side VBA calls, I am stuck on determining this. Here are the calls I use for example know how I can determine if the the field is null using the client side VBA. * Also, using PSI bypasses the local cache and introduces too many issues when creating an number and cost fields as 0 when no value has been entered the Project Server database that holds these can distinguish between a real 0 that has been entered (i.e to local cache as that is all we can safely use for our purposes. The database schema is different than the Project object model in VBA. It was developed at a later date and it manages the data in a different binary file which is what the project application uses. So what is shown in the database is another representation of what is in the file that project stores in the cache

VBA Excel Error with Office 2007 Project I have created a number of vba macros within Project some of which use the Excel Object Library. I am using Project distribute it back to other users who still have 2003 for both Project & Office the vba code no longer works. When Looking at the References I am being told the 12 missing because I only have the 11.0 object (2003). How do I make the vba work regardless of which object model the users have on their machines? Project Discussions Project 2003 (1) Office 2007 (1) Office 2003 (1) Excel (1) VBA (1) Distributes (1) Macros (1) Acca (1) I probably should have clarified. . . . The vba code does work for the users with office 2007. the problem comes when a 2007 project file and distributes it to a user who only has office 2003. Then the vba code no longer works. It is viewable but will not execute. I even tried re 11.0 object model of which it will not allow me to do now. the vba being executed exists within the project file. my only thought is to have users copy

Project Developer Help content Project Hi, I found recently that the help available in the VBA Editor has changed for the worse. It looks nicer, but is content free. For instance office.12).aspx) but it used to be easier to get it directly from the VBA Editor. Pressing F1 on an object or proporty would get you the details, now I 1) The Project Object Model reference (1) Neil, With the release of Project 2007, the VBA help file took a turn for the worse and from a recent comment by one of our premier VBA MVPs, Project 2010 is even worse. I would say that if you find a way you need, (e.g. MSDN), then go for it. If I have to write some VBA code in Project 2007 I revert back to the VBA help file in Project 2003. John Project MVP Me too John, Project 2003 VBA help is much better! Don't forget the object browser as another way to find for Project - http: / / www.project-systems.co.nz Author of the only book on Project VBA, see: http: / / www.projectvbabook.com _ __ __ __ __ _ Information from ESET Smart Security, version of virus signature