Update Master Database Prompt - D-Tools Forum

David_Haddad · 07-04-2007, 09:07 AM

I am going to start with a suggestion I made in the pre-release forum that there seemed to be unanimous agreement on. When I modify a sku in a drawing, let's say I adjust the price as an example, I do not want to be prompted every single time asking me of I want to update the database with the new information. If I wanted to update the database I would be doing so. Not only is the prompt irritating and time wasting, I believe it increases the likelihood that the database will be accidentally changed.

Thanks

**Kevin Mikelonis** · 07-04-2007, 03:25 PM

Originally Posted by David_Haddad

I am going to start with a suggestion I made in the pre-release form that there seemed to be unanimous agreement on. When I modify a sku in a drawing, let's say I adjust the price as an example, I do not want to be prompted every single time asking me of I want to update the database with the new information. If I wanted to update the database I would be doing so. Not only is the prompt irritating and time wasting, I believe it increases the likelihood that the database will be accidentally changed.

Thanks

Agreed!

The amount of prompts for things is out of control in the prerelease.

The worst one is the 'orphan packages' which prompts you to delete and the check boxes for doing so are already checked, one wrong click and all your package names are eliminated. Not good when you are building a database! this actually happened to me during the pre-release testing.

I hope that many of these were removed by David's suggesstion, but since I do not have the final release discs either, I cannot say.

avzone · 07-05-2007, 01:22 AM

Originally Posted by David_Haddad

When I modify a sku in a drawing, let's say I adjust the price as an example, I do not want to be prompted every single time asking me of I want to update the database with the new information. If I wanted to update the database I would be doing so. Not only is the prompt irritating and time wasting, I believe it increases the likelihood that the database will be accidentally changed.

Thanks

I too would like to see this eliminated.

07-05-2007, 05:28 PM

This is a good suggestion that we will take in seriuos consideration for a future release. This was difficult for us to eliminate in V 5.0 with our current data model and how we store project data vs. product/database data. We'll have an easier time eliminating this prompt and streamlining this functionality when our data model is enhanced - something we have slated for 6.0.

David_Haddad · 07-06-2007, 07:04 AM

Thanks for the response Jeff, but I have to ask, is that prompt really related to the current data model??? I'd think that and some of the other prompts are something you are invoking.

07-06-2007, 05:49 PM

Dave,

In 6.0 we'll be able to manage writing to the databases much easier - this will eliminate cumbersome prompts. We'll also investigate what (if anything) we can do with this prompt in 5.1. One quick suggestion maybe a be a global project setting to turn it off (or on) until 6 is around.

JordanC · 07-09-2007, 06:18 PM

I am just putting my notification of acceptance on this suggestion. I said on the earlier post that product modifications should only be made within the database and not the datamatrix. I think this should hold true for the packages as well.

I modify skus and packages every project for notation and I sometimes find myself accidentally accepting the revision to the sku to the database as a permanent change. No matter how careful I am in doing this, I still find myself doing it once or twice a project and not noticing it until a later project.