UPdate Editable in a table

Noelit · 2008-07-22

I want to enable editable property so as to run a report to slah zeros in NAV ](*,) ](*,) ](*,) ](*,) :roll: :roll: :roll: :roll:

Xypher · 2008-07-22

Please rephrase your question... What is it you're exactly trying to do? I assume CurrForm.TableControl.EDITABLE := TRUE; isn't working for you since you're posting this.

Waldo · 2008-07-22

Noelit wrote:

](*,) ](*,) ](*,) :roll: :roll: :roll: :roll:

I think you're annoyed with the fact you can't "slah zeros in NAV"?

I agree with Xypher, you should rephrase your question (I also agree with the fact that "NAV is fun"

, but anyway ...).

After wikipedia-ing it, I guess you mean "slashed zero", no? Then, I think using the font "Consolas", "Miriam", "Rod",... would be a possibility.

Alex_Chow · 2008-07-22

Noelit wrote:

I want to enable editable property so as to run a report to slah zeros in NAV ](*,) ](*,) ](*,) ](*,) :roll: :roll: :roll: :roll:

wow... I had to re-read the question and responses to still not be able to figure out what he needs...

Waldo · 2008-07-22

Yeah, the "editable" property on a report is bothering me :-k

Noelit · 2008-07-23

Waldo wrote:

Yeah, the "editable" property on a report is bothering me :-k

Pliz get this the thing is to slash some digits from the system using a report as the figures have gone to quadrillions so there are a number of fields in the ledger that are set on their property as editable NO so they are skipped when the report runs in the system.Look at this an retailer sales shoes for 300,000,000,000.00 a pair then what would the GL have at the end so to prevent an overflow we are cutting the digits by up to 6 zeros ](*,) ](*,) ](*,) =D> =D> =D> =D>

kine · 2008-07-23

If I understand correctly, you mean "removing zeros from the numbers by dividing them by e.g. 1000 to have smaller numbers able to fit into the editbox and not show them as ****** because the space. But the fields are non-editable and you are asking us if it is possible to edit these numbers through report?"

If it is what you mean, than answer is yes, you can edit these fields through report, but all depends on your license and if you are changing some standard fields, you need to know well what you are doing because all this can have big consequences...

Noelit · 2008-07-23

kine wrote:

If I understand correctly, you mean "removing zeros from the numbers by dividing them by e.g. 1000 to have smaller numbers able to fit into the editbox and not show them as ****** because the space. But the fields are non-editable and you are asking us if it is possible to edit these numbers through report?"

If it is what you mean, than answer is yes, you can edit these fields through report, but all depends on your license and if you are changing some standard fields, you need to know well what you are doing because all this can have big consequences...

Thanks but the license is not an issue the thing is there fields like Amount in the Customer Table for example the property is set to No on Editable so when i run the report it does not slash the figures.NOTEThe figure have passed the area of 500 quadrillion and there can be an overfolw any time soon. ](*,) ](*,) ](*,) ](*,) ](*,) ](*,)

Kowa · 2008-07-23

There is a Divisor property for Controls in Forms and Reports, if you enter e.g. 1000 here it divides the amount displayed correspondingly. Don't forget to change the field caption to inform the user about it.

Savatage · 2008-07-23

The Amount field in the customer table is so you can enter an amount that is billed periodically (a subscription price, for example).

Why not change the property to editable. In fact It's <Yes> by default.

DenSter · 2008-07-23

Noelit wrote:

the property is set to No on Editable so when i run the report it does not slash the figures

The editable property has no effect on reports. What are you talking about when you say "slash the figures"?

Waldo · 2008-07-23

StripeThrough?

I guess my assumption was not correct

Xypher · 2008-07-23

Let me take a stab at this...

(maybe not for the solution but to better describe what I think this person wants.)

Noelit is attempting to run a ProcessOnly Report to slash 0's on large numbers (Overflow size) but the Report cannot do so if the field is set to Editable: NO.

(Am I right? Do I get a cookie?

)

Kowa · 2008-07-23

Xypher wrote:

Noelit is attempting to run a ProcessOnly Report to slash 0's on large numbers (Overflow size) but the Report cannot do so if the field is set to Editable: NO.

Even if a field is not editable you can modify the field values in a report, provided the license allows the modification of the table. The customer license will not allow this for G/L entries (and lots of other ledger tables).

Xypher · 2008-07-23

Well either I made myself look like a bumbling idiot twice in the same topic or by Kowa replying to my post I at least played a role in possibly bringing to light a license issue. (that had previously been brought up; Noelit might have not been aware of the latter mentioning of said issue? :-s)

Either way, I speak no further on this topic O:)

Savatage · 2008-07-23

how did "these numbers" (still unknown) get so large?

and even so is simply changing the value a responsibile move?
what will it effect?

DenSter · 2008-07-23

I was thinking the same thing.... are you going to simply go through the entire database and dividing all decimal fields by 1000?

Xypher · 2008-07-23

Just a thought...

IF Table.BigIntegerVar > ####### THEN BEGIN
  //***HACK & SLASH ZEROS!!*** (code here to make NewVar)
  Table.BigIntegerVar := NewVar;
  Table.BleedingZeros := TRUE;
  Table.MODIFY;
END;

Alex_Chow · 2008-07-23

This may be the longest thread which everyone is trying to figure out what the question is.

ajhvdb · 2008-07-23

Maybe the inflation in his country is so high, NAV can't handle those large decimals anymore. :-s

Xypher · 2008-07-23

ajhvdb wrote:

Maybe the inflation in his country is so high, NAV can't handle those large decimals anymore. :-s

No kidding... 300,000,000,000.00 for a pair of shoes!

Waldo · 2008-07-24

He should specify which shoes he means... :-k

Brand? Type (sports, ...)? Sexe?

idiot · 2008-07-24

Xypher wrote:

ajhvdb wrote:

Maybe the inflation in his country is so high, NAV can't handle those large decimals anymore. :-s

No kidding... 300,000,000,000.00 for a pair of shoes!

Sounds like rupiah...
Anyway this large numbers matter is no joke...been enlarging a lot of fields & converting a lot of reports to landscape because of display purposes...

Kowa · 2008-07-24

If really every single amount has to be divided, the best way is to use the Euro Conversion Tool and adapt that for your country version. Every european database in the eurozone that was started before 2002 had to go through this.

Noelit · 2008-07-24

Kowa wrote:

Xypher wrote:

Noelit is attempting to run a ProcessOnly Report to slash 0's on large numbers (Overflow size) but the Report cannot do so if the field is set to Editable: NO.

Even if a field is not editable you can modify the field values in a report, provided the license allows the modification of the table. The customer license will not allow this for G/L entries (and lots of other ledger tables).

Guys the License is not an issue,all the relevant granules are there, its just that the Figures here are a bit wayward to most of you bcoz of yo economies.I can manually do the process of changing the property but was looking at a scenario where i can just change the property during runtime as what happens when a form using the Update editable property ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) ](*,) :shock: :shock: :shock: :shock: :shock:

DenSter · 2008-07-24

Once more.... the editable property of a field has NOTHING to do with whether you can modify the value through C/AL code. Even when a field is set to be non editable, you can still modify the value by programming it.

Eugene · 2008-07-24

i suggest you enter a new currency RupiMln which is exactly 1000000:1 to rupi and then use RupiMln

Alex_Chow · 2008-07-24

My last crack.

Are you talking about the DecimalPlaces property?

DenSter · 2008-07-24

Alex Chow wrote:

My last crack.

You have more than one? :shock:

Slawek_Guzek · 2008-07-24

A little off-topic:

ajhvdb wrote:

Maybe the inflation in his country is so high, NAV can't handle those large decimals anymore. :-s

100% hit.

Inflation in Zimbabwe this year reached 2 200 0000 per cent (two million two hundred thousands). That's official Zimbabwe's government information. Unofficially it is expected to be bigger.

Regards,
Slawek

Alex_Chow · 2008-07-25

Are there any companies in Zimbabwe that uses Navision? :-k

UPdate Editable in a table

Comments

Categories