Re: Determine Least Significant Digits - C# Discussion Boards

Jassim Rahma7-Dec-09 2:12

7-Dec-09 2:12

i have an off topic question and want to know your advise..

I am using C$ and i want to know what's recmonnaded in order to have the best result?

should I save the debit and credit in a table in the same field (trxn_amount with + or - sign? or save them in separate fields (trx_amount_debit and trxn_amount_credit?

Re: debit & credit question [modified]

Eddy Vluggen7-Dec-09 2:52

Eddy Vluggen

7-Dec-09 2:52

jrahma wrote:
should I save the debit and credit in a table in the same field (trxn_amount with + or - sign? or save them in separate fields (trx_amount_debit and trxn_amount_credit?

What do you mean with "best result"? From a developers' perspective, things that are the same go into the same table. Splitting them into separate tables gives no advantages that I can think of.

--edit--

I'd simply derive the credit/debit type from the amount, e.g., everything positive is credit. Developers don't store the same information twice. So, from a dev's view, storing the credit/debit type is redundant if it's value can be derived from the stored information.

Now, I have been told that this is inconvenient for reporting, and that it's rather convenient to have a flag in the database that indicates the direction of the transaction. The thing I missed, is that I could be credited $-1, and that would be something completely different from being debited a dollar.

I are Troll Suspicious | :suss:

modified on Monday, December 7, 2009 11:38 AM

Re: debit & credit question

Sunil G7-Dec-09 2:56

Sunil G

7-Dec-09 2:56

You should seperate field to store debit/credit type.
Value should be either Dr or Cr

Re: debit & credit question

yousaf287-Dec-09 3:50

yousaf28

7-Dec-09 3:50

save it in a same table with +ve and -ve sign Smile | :)

Re: debit & credit question

Shameel7-Dec-09 7:23

Shameel

7-Dec-09 7:23

Use separate columns to store debit and credit values.

If you are asked to get totals of debits and credits, you just do a SUM() without a need for WHERE clause.

Since the values have a wide distribution of data, indexes created on these columns tend to be larger. The separate column solution avoids creation of indexes on these columns.

Re: debit & credit question

Gerry Schmitz7-Dec-09 18:42

Gerry Schmitz

7-Dec-09 18:42

"Classic" bookkeeping / accounting reports and forms always show the Debits and Credits in separate columns.

While your calculations for figuring out "account balances" may require a bit more work, your reporting requirements, GUI / Forms design, and batch balancing are greatly simplified.

(The DBA types will shriek in horror, however)

Determine Least Significant Digits

MumbleB7-Dec-09 2:08

MumbleB

7-Dec-09 2:08

Hi Guys. I need to know how to determine the least significan't digits from a number. Now, I'm calculating a bunch of numbers and the total comes to say 17 digits in total. I need to only use ythe last significant 12 digits from the 13 digits. HOw do I determine what the least significant digits are?

As an example:
The calulated value is: 865807311427710

From this number I want to only obtain 807311427710.

The problem I am having is that the calculated value can be any amount of digits long.

Any help will be greatly appreciated.

Thanks

Excellence is doing ordinary things extraordinarily well.

Re: Determine Least Significant Digits

OriginalGriff7-Dec-09 2:13

OriginalGriff

7-Dec-09 2:13

Brute force and ingnorance approach: Convert to a string, use substring to get the right hand end.

No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced.

This message is made of fully recyclable Zeros and Ones

"Rumour has it that if you play Microsoft CDs backwards you will hear Satanic messages.Worse still, is that if you play them forwards they will install Windows"

Re: Determine Least Significant Digits

MumbleB7-Dec-09 2:19

MumbleB

7-Dec-09 2:19

Sounds easy enough but the problem is that I have no idea how long the string will be. It could be 20 digits, 30 digits, 15 digits or 12 digits. Sigh | :sigh:

Excellence is doing ordinary things extraordinarily well.

Re: Determine Least Significant Digits

OriginalGriff7-Dec-09 2:28

OriginalGriff

7-Dec-09 2:28

So? Why would you care?
number.ToString() doesn't care how long it is.
string.Length tells you how long the other one is.
You know how many digits you want to keep...

Re: Determine Least Significant Digits

MumbleB7-Dec-09 2:40

MumbleB

7-Dec-09 2:40

Aye, I got it. Below is what I have done.

FinalHash = homingTotal + OverFlow + ContraHash;
string hashfinal = Convert.ToString(FinalHash);
int length = hashfinal.Length;
int remove = length - 12;
outhash = hashfinal.Substring(remove, 12);
finalhashtotal = Convert.ToInt64(outhash);

Excellence is doing ordinary things extraordinarily well.

Re: Determine Least Significant Digits

Covean7-Dec-09 2:29

Covean

7-Dec-09 2:29

How about

long lDigits = lCalulatedVal % 1000000000000;

this should do the trick.

Greetings
Covean

Convert a structure to a byte array (C# 3.5)

stefanidou7-Dec-09 1:30

stefanidou

7-Dec-09 1:30

Hello

Could you please help me to make a convertion from a structure to byte array?
Is there any function to do that?
I would appreciate if you could give a short sample of code Smile | :)

Thanks

Re: Convert a structure to a byte array (C# 3.5)

Abhinav S7-Dec-09 1:34

Abhinav S

7-Dec-09 1:34

http://www.developmentnow.com/g/36_2009_10_0_0_205962/How-to-convert-a-structure-to-byte-array-.htm[^]

Generating a Unique ID.

farshad1237-Dec-09 1:00

farshad123

7-Dec-09 1:00

I want to generate a Unique ID as this. Unique ID Should Look like this "CID-00001,CID-00002,CID-00003.....".

I need a class to generate this. First i need to check the database for the previous ID.

If there is No Data it should generate the ID as "CID-00001" else it get the last ID and increment it by one and store it to the database.
I need the C# code for this.

Thank you.

Re: Generating a Unique ID.

dan!sh 7-Dec-09 1:03

dan!sh

7-Dec-09 1:03

Have you tried anything?

50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!

Re: Generating a Unique ID.

Ashfield7-Dec-09 1:10

Ashfield

7-Dec-09 1:10

Yes, posted a question here in the hope of somebody giving him the code Smile | :)

Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP

Re: Generating a Unique ID.

dan!sh 7-Dec-09 1:13

dan!sh

7-Dec-09 1:13

50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!

Re: Generating a Unique ID.

farshad1237-Dec-09 1:20

farshad123

7-Dec-09 1:20

no i didn't.

Re: Generating a Unique ID.

OriginalGriff7-Dec-09 1:37

OriginalGriff

7-Dec-09 1:37

Well it has the advantage of honesty!

Not enough to just give you the code, but at least it's honest.

First: Decide what database system you will use. What have you got to play with?
Second: Create a table in the database, create a field in the table.
Third: Write code:
Third.First: Connect to database
Third.Second: Read from database, identify highest existing entry
Third.Third: Increment enty to create new one.
Third.Fourth: Add to database, check for error.
Third.Fifth: If error, repeat from Third.Second.
Fourth: Use new entry as number.

There are other ways to do it, but that is the basic idea.

Re: Generating a Unique ID.

Abhinav S7-Dec-09 1:16

Abhinav S

7-Dec-09 1:16

Try searching for GUID on msdn. You might get what you want.

Re: Generating a Unique ID.

Ashfield7-Dec-09 1:19

Ashfield

7-Dec-09 1:19

Abhinav S wrote:
You might get what you want.

But I doubt it when he doesn't want guids. The OP says Should Look like this "CID-00001,CID-00002,CID-00003.....", which are not GUIDS (but are dead easy to generate anyway)

Bob
Ashfield Consultants Ltd
Proud to be a 2009 Code Project MVP

Re: Generating a Unique ID.

Abhinav S7-Dec-09 1:31

Abhinav S

7-Dec-09 1:31

Then I suppose its just a lot of homework Smile | :)

MS OFFICE refence version create problem to change code of program

ishika_kukki7-Dec-09 0:14

ishika_kukki

7-Dec-09 0:14

hi all,
i m working in a desktop application in which i added reference of MS WORD DLL and MS EXCEL DLL, and all reporting is Done in Word File and Excel File, project is working fine but whenever we installed program in any other system which contain MS OFFICE of other version an error generated,
Example: -

if i include reference of ms office 97, word ddl than i open exiting file as
WordDoc = new Word.Document();
WordApp = new Word.ApplicationClass();

WordDoc=WordApp.Documents.Open(ref filename, ref missing, ref readOnly,
ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing);
WordApp.Visible = true;

if we include reference of ms word XP dll than we open file as

WordDoc=WordApp.Documents.Open(ref filename, ref missing, ref readOnly, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref missing, ref isVisible, ref missing, ref missing, ref missing);
WordApp.Visible = true;

simiraly MS OFFICE 2003
includes some more parameter for OPEN method

my problem is that how can we include a Reference which work same for all version, because for every version of OFFICE we cannot make seperate code

thanks
in VB 6.0 we hav to add or change only reference and no need to change in code, but in C# .net i have to change the code as well as Reference of Office DLL.

thanks pls help me

Re: MS OFFICE refence version create problem to change code of program

dan!sh 7-Dec-09 0:46

dan!sh

7-Dec-09 0:46

I think you can make use of late binding here. Or have something like:

// Check Office version

if(Office 2003){
// do something 
}
else if (Office 2007){
// do something else
}
else{
// why don't you upgrade your office version?
}

50-50-90 rule: Anytime I have a 50-50 chance of getting something right, there's a 90% probability I'll get it wrong...!!

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.