-
Amol, you should probably take a class about SQL Server, or read a book or something, because it is clear that you do not understand some basic principles. The SQL Server shrink functionality DOES NOT truncate the log file, and detaching and deleting the log file is not the right way to solve this. To free up the content of the log file, you will need to do a log backup. For a test database that you don't need to back up, you could also set the recovery model to Simple.
-
Amol: how can you miss the customization, do you not tag custom code with comments?
-
Amol's example is wrong. The Location Code field does not update on the lines. The message does not give you the choice to update the lines, there is only a message that you will need to update the Location Code on the lines manually. There is a function called UpdateSalesLines in the Sales Header table that takes care of updating related sales lines. You will need to add logic to that function to take care of the custom field, and add a call to the function to the OnValidate of the custom field
-
Watch this: http://youtu.be/0KbZkKdyZps
-
The work date does not automatically update like you are saying. It sounds to me like they leave their NAV session open overnight. Restarting the NAV client should take care of that. If it's not absolutely necessary to leave the session open, I'd think about putting in place logic that automatically logs people out after a certain idle time.
-
Don't be too hard on yourself :) even if you had known about that you'd still have wondered about whether the workdate gets updated. Glad to hear you got to the bottom of the issue.
-
The way that I would approach this: First I would debug the scenario in which the field is populated, so that I know what exactly causes the field to get a value. Next, I would debug the scenario where the field is NOT populated, to figure out why that happens. The difference between the two will give you the explanation of why. The next step is to come up with a way to fix it. It probably has something to do with not validating the Quantity field when the copy doc function is run. The trick is though
-
Nah people are equally smart (or equally dumb) wherever you go Intelligence is not related to the product that you work with. There are extremely smart people working with NAV, and there are extremely stupid people working with SAP/Oracle. If you want proof ask yourself whether you became smarter when you switched or not. About earning potential, it feels like you are looking for free money, which is the wrong way to look at it. There is a fair bit of luck involved in running into the right opportunity
-
The same thing applies, any job in the Oracle business (assuming it's with a good company) is good, there are many things to do in that business, just like in NAV, with tons of opportunities worldwide. If you are a developer you will probably have big problems adjusting to a consultant role though, so I'm not sure if you would be successful or not by switching from development to a functional role. Doesn't matter really, if you start with something new you have to learn everything.
-
My pleasure Asharaf :)