Search results

Open the report in design mode. Select the text box containing the field you are trying to change Right-click select properties from the popup menu look on the Format tab for the 'Format' property. Select 'Currency' look on the Format tab for the 'Decimal Places' property. If necessary...

Actually, that's been the accepted way to roundoff since the Fortran and COBOL days.

watch those zero's! Int((MyNum/1000000)+0.5)*1000000

Did you try this ...? Sometimes changing the format at the table level does not fix up forms and reports. You can always force or override a format at the individual control by changing its design properties.

Setting an input mask doesn't make much difference if you are importing. The data is arriving in pennies rather than dollars. You have three choices: 1) Create an update query and divide the values in the table by 100 EACH TIME you import. This is clumsy and you run the risk of accidentally...

Divide the number by 100 as you are doing, and then FORMAT the control to display two decimal places

You were supposed to substitute YOUR names for the form and subform where Rich said 'MainFormName' and 'SubFormName'!

Close... How about something like: ROUND(MyNum/1000000)*1000000

I don't know if this is good style, but I have a database with a great number of text and numeric 'constants' used in other calculations, forms, reports, etc. I created [tblConstants] with 5 fields: [ConstantID] - autonumber PK [ConstName] - short name of the constant, uniquely indexed...

I don't think you want the 'ratio' control to be bound, if you are just using it on your form to calculate one of the other two. In the AfterUpdate event of the form, you can add some code to calculate the third (i.e null value). I would have the routine check to see if exactly two of your...

You can find a large number of ways to create a virtual WINDOWS keyboard, that can be used in Access or any other windows app by going to a general search engine like Google and typing: windows virtual keyboard

BTW, you guys have a 17.5% VAT !!?

The rounding rule I was taught in school was that when the last digit is a '5', you should round to the even (i.e. 0,2,4,6,8) value, sometimes rounding up, and sometimes down. This was so that statistically, the average effect of the roundoff would be zero, given a large sample. Perhaps...

You are trying to set up a table and a means of cross-referencing the same table. In your 1st table, add a primary key autonumber field (call it RuleID) with a unique ID number. You can have your rule name be unique as well, but some things in Access work more smoothly if you link using...

try http://www.accessdatabaserepair.com/ They may be able to help you for a very reasonable fee. If you made a copy of your corrupted database before you tried to 'fix' it, they will probably have an improved chance to recover your data as well. [ end free plug for forum owners ;) ]

I have a database under development where I use a Gantt Chart. The date range and scale of the graph are adjusted 'dynamically' via controls on the form and some event-driven code. Ignore most of the rest of the db as it is still a work-in-progress See the attached HTH

My response in this thread may be of interest: http://www.access-programmers.co.uk/forums/showthread.php?threadid=41357&highlight=gantt

skunk711: You have now described a FIFO. To do a Weighted Average: What I would do is create a couple of fields in your stock item master table (NOT your transaction table). Lets call them [QuantInStock] and [ValueInStock]. The unit price can be easily calculated in a query as UnitPrice...

After you remove all of the records from the table, compact the database. The first record you enter should then have an autonumber value of 1.

Correct me if I'm wrong... If a transaction is a removal from stock, then the weighted average price is unaffected. If a transaction is an addition to stock (either a receival or a return), the a new weighted average need to be computed. The formula for the new price would be something like...