Anyway, here's the splash screen to whet your appetite :)

It's coming along nicely but am trying to make it a polished product that doesn't look like a average old database, but is more geared towards users who are accustomed to a more program like interface.

Current features :

• Track addon products for multiple Programs
• Track Product assocations (ie what add ons require what products to work).
• Track bundles
• Track installed files (not automated as yet unfortunately, Trying to find out if it's possible to track extraction programs and where the files go to).
• Multiple categories, descriptions, Hyperlinks, Email Addresses and Preview images (or you don't have to put this info if you don't want to).
• Manage projects (File assocated, programs used, products it's associated with etc).
• Product wish lists

Anyways, catch ya all later :)
Cheers

This sounds really promising, starmage!  Please keep us informed on its progress.

wish I'd had this 23,000 items ago..;) Access only goes so far..;)

Sounds familiar.  I'll be interested in what you come up with.  I link to applications that do what the PDT does because no program will fill all niches (and mine definitely doesn't).  When you get it done, send me a link via site mail and I'll put it on my site.

Yeah it might sound a bit familiar :)
I started looking into this and what people wanted in such a database about 2 years ago.  Unfortunately I lost interest for a while but it's been a pet project of mine and I hope to get it finished by mid year.  Theres actually a lot of programming involved.

lol pakled.
That's what got me started....

This one is part of the setup process......

Looks very promissing :D

This is the full setup wizard for you to see.

Also have most of the tables in and linked properly.

Sweet!  Can't wait until it's done.  I'd love to give it a good go since I've got so many things going on right now.  This should prove invaluable in managing my projects and products.

It's rather complex so if you're not an Access nut maybe better not  try to decipher it.

Ok well the Project Management tables are now in.

Some of the basic features of the Project Management will be :
  - Track File Assocations
  - Track which Products it requires
  - Track which Programs it requires
  - Project Description
  - Artist(s) working on the Project
  - Project Preview images
  - Project types (ie modelling, texturing etc)

Some of the more advanced features :
  - Project completion wizard (Moves it over to the Products table for you)
  - Automatic Readme file creation (including Copyright, Terms of Use and File list).

Note that the whole database will be using a split design (Back end and Front end) which means if you have multiple artists working on different computers over a Network, all can access the same information from the back end..... (Supposedly, this is my first try at this).

I should also point out that just about every peice of information is "Optional" (hence the rather complex design).

Starmage,

Simply awesome. I want to thank you for all of your hard work.

Just one word for you, Starmage ... SWEET!!!!!!!!!!!!!!!!!!!!!!

Thanks for all your work with this.  I can't wait.

Hi All
Took a slight break from doing the database and delved into Poser 7.  There's nothing quite as relaxing as pumping out a little bit of creative work :) .  Well it's more relaxing than programming a database anyway!!!!!! lol  Besides I can always use some of my art in the actual Database.

Anyway.......
Bit of a question about the automated creation of a Readme file......

The actual process of doing this is easy enough, but it's the process of creating the template that's not.  I need a pretty basic idea of what you'd expect in a Readme file for a product?

I'm thinking you'd need.....

1. Introduction (General Description of the product)
2. Requirements  (Automated)
3. Installation Instructions
4. Copyright Information
5. Terms of Use
6. FIle List (Automated)

Apart from that I'm also of the impression that the actual readme file needs a specific name that partains to the actual product.  (Note my recent frustrations about older Readme's being overwritten by new installs of other products because they're not named specifically for the product).

Yes, I always give my readmes a name of the form readme_nameofthing.txt for just that reason. I'm wondering if it might not be better to use readme_author_nameofthing.txt in order to avoid clashes when two people make the same thing. The content varies, but the usual layout covers the following: - Name of thing, and brief description (including whether a particular Poser feature is required) - Installation instructions - Specific usage instructions -- Materials -- Morphs -- Special features etc. - Terms of use -- Renders: commercial or personal? -- Add-ons: (morphs, textures etc.) allowed or limited? -- Redistribution: allowed or not, and if so, under what conditions? - Contact details

Ok kewl Bob
Assuming one would take advantage of the full features of the database most of that could be automatically added.  Like the Name/Description and the requirements.  And I suspect the Installation instructions would be pretty "Generic" in most cases.

Not to sure about the special features etc....
That might have to be added specifically.

The Terms and Usage and stuff I also think would be pretty well covered by a "Generic" bit that could be determined by whether the product is Free or commercial and whether it's just for Personal use or commercially usable.

Info could always be piped through into a textbox on a form and people could "Adjust and edit it from there.  But even that would allow for the removal of the more tedious components of the actual creation of stuff like the File lists/Installed components. 

I just noticed office 07 has a translate function so i could even provide the basics in multiple languages (Not sure if that would be useful though).

This is the template I use in all of my readme files - both for sale and free.  This is the one that is approved by Renderosity and works on all of the other sites with only minor changes (like the site license).

Product Title: Name of Product
Author: Victoria Hall  (Victoria Lee)
Author E-mail: victoria85015@cox.net
Product Date: Date of Creation
Product Copyright: Digital Imagination & Victoria Lee; Year

Ownership statements or list of licensed source material:

• Copyright Information (merchant resources, etc)

Needed Files List and System Required:

• Poser 5 and higher
• Characters needed for product
• Windows/Mac OS Compatible

Detailed Installation Instructions

• Extract the zip-archive with your zip program:  Open WinZip and press the button Extract
• In the window -Folders/drives-, select the folder that contain your Poser runtime.
• (ex. C:Program FilesCutious LabsPoser 6).
• You can also install to an external runtime using the same method.
• The check box -Use Folder names- must be marked.  That way, all files will placed in the correct path.

Usage Instructions:

• Specific Usage instructions and Limitations
   

Packing List:

Files and locations

RuntimeDI_Readme
DI_productname_readme.txt (this file)
Renderosity License.txt

The product does not require conversion

Thank you for downloading this package.  Feedback is greatly appreciated.  Please contact me using site mail. 
<<

Yeah okay could be made to be Distributor dependant too I suppose.  Anyway I need to get back into it cos I took a break (Had a Psych assignment due yesterday and a test next week).

Presently am trying to concentrate on the interface design.  And tweak the actual Database backend.

But I suspect an approach to doing this particular function would be a wizard that would let you choose what particularly parts you want to add/leave out beyond the necessary basics and more advanced bits could be added later to the file if necessary.  Either through editing in notepad or through a textbox on a form.