Search results

I haven't read the whole thread. Maybe this has been dealt with. surely rather than colour=blue you would use colour=cstr(vbblue), (or more simply just the numeric string, and then dereference the string back to the numeric value in your class.

Because of rounding issues, and for the avoidance of doubt I would definitely store the invoice and sales tax total declared in your accounts within the invoice table. I appreciate it can be calculated, but the rounding effect introduces an ambiguity that you don't want in legal accounting...

First, I would definitely store an invoice total on the invoice record, then you would avoid the problem of the totals query. You also need a paid so far, or an outstanding amount which takes into account part payments. If the payment doesn't completely pay an invoice though, you have to do...

^^^ I don't think you are missing anything. It adds a little complexity but it also allows you to do rolling and selective stock checks.

You don't have to adjust inventory on all items simultaneously. The product can carry a stock take date, and the transaction records can store the opening stock count (and maybe value) for individual items. So you can then sum the movements since the last stocktake for each item.

That would make sense in any event. A stock take adjusts the calculation for any errors, and gives a sensible base point for future calculations.

I would add code that tests and reports on whatever mechanism you use to maintain a persistent connection to the database. I add a button to the dashboard to check the position. ie, that the object I use is not nothing.

I imagine the issue is that the 64 bit is now the default, and not many people need to deal with the differences. I have apps in use that's built in 32bit, and I don't want to try to convert it to 64, so users have to install 32bit office to use the databases.

Transparent buttons are still clickable I think.

If you don't set a database as a trusted database/location it will always warn you when you open it. The runtime doesn't let you set it as trusted, so you have to authorise it each time it opens. It's a minor inconvenience in order to use MS Access as free software, I believe.

I agree with this. I'm sure I've seen error messages like "you can't set the focus to a hidden control".

An arbitrary number. A specific number rather than the next autonumber provided by the seed. As I say, I don't think you can do this with SQL Server.

In Access you can just write an append query and force the ID to be written as any arbitrary value, such as 3. I think SQL server for instance won't do this behaviour .

@jwcolby54 I am not trying to do anything. I was just discussing some points raised in the thread. I never try to ascribe "sense" to an autonumber. If I want an intact sequence, I use an appropriate technique.

This bit. That's not correct. The order of the autonumber IDs corresponds to the order in which records were inserted. It's not random. If you insert records to fill gaps, then that's no longer correct. That's the point I was trying to make.

You can poke/stuff autonumber IDs into a table to fill gaps, but then your records won't be in the logical order that they should have been.

@dullster If you want the record ID to be kept in sequence and the sequence to be intact, then you can't use an autonumber. You need to manually control the sequence. I imagine this has been pointed out already. You also can't delete records, or you will get gaps.

Well FIFO comes into it because if you buy your widgets for 1.00, then the next lot are 1.02, then 1.05 the cost of the inventory should be evaluated by counting back the cost of the most recent orders. (Starting with the 1.05 batch). The corollary is that the absorbed cost of sales/production...

For what it's worth, an AI answer gives the following as acceptable valuation methods for inventory under International Accounting Standards. My understanding is that FIFO is the generally accepted method, although I no longer have to deal with such issues. Edit. Although there are other...

Quantity management of inventory is straightforward. Cost management is decidedly not. FIFO is the method that meets accounting standards, but will be very hard to code, because you need to manage the sequence of both goods received and goods issued.