No - nobody can perform SQL queries from within the Dynamics GP application, and nobody can use their GP login and password to log into SQL - the password of your SQL login is encrypted with a strong encryption.
"As the parent mentions, NO USER has DB access in an ERP system. Only the ERP system itself has access and then the ERP system manages all table and transaction access. Can anyone verify this for GP? Also, even if the system password is available to any user created in GP I don't think that matters."
As far as Dynamics GP is concerned, all users set up in the system have full read/write access to all tables. The security layer comes from the encryption of the users' passwords by GP for their SQL login. This is done using a strong encryption method, not a caesar cypher.
The original poster, I think, caused a bit of a stir here because I think 101 people here are mistaking the "system" password (which is a weak security password for opening certain system windows, of which all of them would be locked down by the normal security in GP anyway), and the 'sa' password, which truly does have "god" powers in the system.
The business world will eventually learn that hacks throwing together craplets costs them far more time and money then a few talented developers doing it right the first time. Or they will continue to throw money at the problem, expecting that just getting 30 warm bodies that know how to press the right buttons in the right IDE will be a good strategic plan. Chances are the truth won't be realized until they go out of business.
Actually, I am a project manager in the "real business world".. I can tell you where the "craplets" come from, and it's not the programmers using the IDEs, it's those "pureists" that refuse to use the tools given to them.. Sure, their syntax is perfect and they know the language.. Hell, they might even know how to allocate memory to a program under MS-DOS without causing fragmentation with a nifty little assembly APP, but none of that makes a multi-million dollar project succeed - it is the programmers that can collaborate properly and follow a project plan as given to them from me.. (no, CVS and makefiles don't do this - logical project mangement does this - something better handled by an IDE than by a bunch of files thrown into a bunch of folders)..
The IDE assists in dealing with a project's assets properly as well as code-completion and debugging.. This way programmers can spend more time on learning algorythm efficiency, proper encapsulation techniques and modularization and, above all, efficient programming techniques.. There's no reason an IDE has to get in the way unless it is seen as a simple tool like a screwdriver, not a complex tool like a nuclear reactor.
Check out www-csfy.cs.ualberta.ca to see one of the best-designed intro to Java courses in the world (University of Alberta - one of the world's most respected CS departments).. They teach from end-to-end using the Eclipse IDE (www.eclipse.org)..
The catch is that you need to teach the IDE in the OOP context.. IDE's (not glorified text-editors like VI and Emacs) are designed to help keep track of assets as well as the programming style.. If you teach the methods and algorythms using the IDE as a means rather than an ends to proper programming, you will spend less time on the details and more time on real skills like proper data design and efficient programming (unfortunately, something many of the self-taught philosophers you see in these forums lack)
Re:Patents should be abolished.
on
Apple Sues Creative
·
· Score: 2, Interesting
If you are really innovating, your only reward should be to have the advantage to reach a market first. Once your thing is out in the open the game is on and anybody should be able to copy it.
If the contraption is really innovative, then replication should be non trivial, thus permitting the inventor to benefit for longer or to literally sell the invention.
If the contraption is a piece of crap (Amazon: I am looking at your one-click nonsense) then everybody and his dog will copy it because it would be too obvious.
Probe me wrong, why do we need patents?
Oh wait, to give jobs to the bureaucracy that leeches from the system. My bad....
Many inventions which are vital to the world are often trivial to reproduce but cost millions of dollars and thousands of hours of time to actually invent (drug technology falls in this arena).. The alternative to the granting of patent protection is that such inventions would never exist in the first place because nobody in their right minds would invest money in such development.. In your world, I hope you never get cancer, because there wouldn't be 10% of the available treatment or research done that has been done because drug companies are protected by patents..
The purpose of Patents is to make sure that innovation actually happens and innovative products actually become available to the public domain.. They do this by making an avenue where inventors can publish the details of their inventions, get 20 years to control their inventions and profit from their hard work, and then have the details become public domain.. In a time when there was no patent law, inventors had no way to safely share or even produce their work, because they would be undercut by people who didn't need to pile all the time and money in the act of actuall inventing it.
As much as patents are designed to place a disadvantage to consumers, in reality consumers would be worse off if inventions couldn't be patented.. 20 years of catering to those who actually do the work to invent something is a good trade-off against the thought of such things not ever being invented in the first place.
While the resulting litigation is a pain to those who do a lot of R&D, it is their ultimate responsibility to ensure that what they are working on is not already protected - details of patents are publicly available.. If you don't take time to look and act accordingly, you deserve to get your ass handed to you in a lawsuit.
Because everyone uses MySQL... Didn't you know, open source is the only way to go with databases.. Because a thousand cooks with no direction is much better at developing database software than one company that's been doing it for decades!
Of course, you might also get what you pay for.
Slashdot Mirror
No - nobody can perform SQL queries from within the Dynamics GP application, and nobody can use their GP login and password to log into SQL - the password of your SQL login is encrypted with a strong encryption.
"As the parent mentions, NO USER has DB access in an ERP system. Only the ERP system itself has access and then the ERP system manages all table and transaction access. Can anyone verify this for GP? Also, even if the system password is available to any user created in GP I don't think that matters." As far as Dynamics GP is concerned, all users set up in the system have full read/write access to all tables. The security layer comes from the encryption of the users' passwords by GP for their SQL login. This is done using a strong encryption method, not a caesar cypher. The original poster, I think, caused a bit of a stir here because I think 101 people here are mistaking the "system" password (which is a weak security password for opening certain system windows, of which all of them would be locked down by the normal security in GP anyway), and the 'sa' password, which truly does have "god" powers in the system.
Actually, I am a project manager in the "real business world".. I can tell you where the "craplets" come from, and it's not the programmers using the IDEs, it's those "pureists" that refuse to use the tools given to them.. Sure, their syntax is perfect and they know the language.. Hell, they might even know how to allocate memory to a program under MS-DOS without causing fragmentation with a nifty little assembly APP, but none of that makes a multi-million dollar project succeed - it is the programmers that can collaborate properly and follow a project plan as given to them from me.. (no, CVS and makefiles don't do this - logical project mangement does this - something better handled by an IDE than by a bunch of files thrown into a bunch of folders)..
The IDE assists in dealing with a project's assets properly as well as code-completion and debugging.. This way programmers can spend more time on learning algorythm efficiency, proper encapsulation techniques and modularization and, above all, efficient programming techniques.. There's no reason an IDE has to get in the way unless it is seen as a simple tool like a screwdriver, not a complex tool like a nuclear reactor.
Check out www-csfy.cs.ualberta.ca to see one of the best-designed intro to Java courses in the world (University of Alberta - one of the world's most respected CS departments).. They teach from end-to-end using the Eclipse IDE (www.eclipse.org)..
The catch is that you need to teach the IDE in the OOP context.. IDE's (not glorified text-editors like VI and Emacs) are designed to help keep track of assets as well as the programming style.. If you teach the methods and algorythms using the IDE as a means rather than an ends to proper programming, you will spend less time on the details and more time on real skills like proper data design and efficient programming (unfortunately, something many of the self-taught philosophers you see in these forums lack)
Many inventions which are vital to the world are often trivial to reproduce but cost millions of dollars and thousands of hours of time to actually invent (drug technology falls in this arena).. The alternative to the granting of patent protection is that such inventions would never exist in the first place because nobody in their right minds would invest money in such development.. In your world, I hope you never get cancer, because there wouldn't be 10% of the available treatment or research done that has been done because drug companies are protected by patents..
The purpose of Patents is to make sure that innovation actually happens and innovative products actually become available to the public domain.. They do this by making an avenue where inventors can publish the details of their inventions, get 20 years to control their inventions and profit from their hard work, and then have the details become public domain.. In a time when there was no patent law, inventors had no way to safely share or even produce their work, because they would be undercut by people who didn't need to pile all the time and money in the act of actuall inventing it.
As much as patents are designed to place a disadvantage to consumers, in reality consumers would be worse off if inventions couldn't be patented.. 20 years of catering to those who actually do the work to invent something is a good trade-off against the thought of such things not ever being invented in the first place.
While the resulting litigation is a pain to those who do a lot of R&D, it is their ultimate responsibility to ensure that what they are working on is not already protected - details of patents are publicly available.. If you don't take time to look and act accordingly, you deserve to get your ass handed to you in a lawsuit.
Because everyone uses MySQL... Didn't you know, open source is the only way to go with databases.. Because a thousand cooks with no direction is much better at developing database software than one company that's been doing it for decades! Of course, you might also get what you pay for.