Make Break down to contract items in invoice form

but still "Item_Value_Previous" get sum of both items
i used this Expression before
Code:
Previous: DSum("[item_value_current]","inv_contract_details","[contractcode] = " & [ContractCode] & " AND [item_code] = " & [item_code])
and it was working but don't know what happend
 
Hi

As explained previously you cannot use [item code] in your DSum because each record will have a different Item Code value (Item Code is a Primary Key)
 
Hi

As explained previously you cannot use [item code] in your DSum because each record will have a different Item Code value (Item Code is a Primary Key)
thank you Mr Mike i have changed item code in inv_Contract_details table to number and make new field Id and make it the primary key instead and now it's working well
 
Hi Dears
i want to set "item_Value_Current" to null every new invoice so i can write the new progress value
you can use invoice to "Engineering for the Petroleum and Process Industries - Enppi"
and project name "Abo Rudes" for try
another thing if possible i want to move the total of "item_Value_Current" which appeared in the form in Text343 text box
to "Current" text box with notice that the event of invoicing after update "Current" text box
 

Attachments

I added code to the Save Invoice Button but you still have problems with your append query.
it has to be in different button cause the events of calculation in " Current " not working now try to write any value in current to get what i mean
about append query if you change the value in current it will work fine
also the value in "item_Value_Current" still have value when choose project
 
i think it's better now the value moved when click move the value button and click on invoice value field to make the calculations
any better idea ?
 

Attachments

Sorry but someone else will need to take a look at this, as I am completely lost with your process,
 
Beats me why you need such huge variables, forms and no doubt table and field names Mobarak.
Aim for 8 max is my advice. What is wrong with IvalPrev ?
 
Beats me why you need such huge variables, forms and no doubt table and field names Mobarak.
Aim for 8 max is my advice. What is wrong with IvalPrev ?
it's for contract clients accounting , all this tables i need it in my work
 
it's for contract clients accounting , all this tables i need it in my work
I understand that Mobarak......I think. But your references in Queries, IIF() Functions etc must be a mile long. (or maybe 1.6Km!)

From the 1980s through to the end of 1990s, using MS-DOS you couldn't have a filename longer than 8 characters, let alone
field names and variables.

Whilst some may find this restrictive by current coding rules, it did have advantages in forcing clarity in creating file and
variable naming techniques. The file and variable naming systems that I developed nearly 40 years ago I still use today, but
with slight variations due to Access and SQL type databases.

Only the other day @isladogs strongly advised against using spaces in names, which is good advice to be followed.
However, far from it for me to tell you what to do Mobarak, I just think that you could benefit from using shorter names
in future. But as I say, your choice.
 

Users who are viewing this thread

Back
Top Bottom