Search results

Surely one problem is that developers end up giving way stuff that's taken them a lot of hard work to develop. For example, it really was difficult to find and build parts of an application to manage interfacing with a Restive API instance in Access VBA, and process the JSON responses. It was...

I had some excel files that Access didn't like. They had been produced by SAP, I think. Do you know what system produces the files causing your problems. What file types are they? Can you get csvs instead?

Maybe there's something funny in the column headers for your version 20. Underscores, or something like that. Maybe it's the full stop/period in the file name causing confusion. In fact, can you have a period in a file name?

In general cleaning large amounts of dubious data is not going to be easy.. If it's an ongoing issue, then I still would explore considering a table based control system, as you could freeze the current problems and work on them without continuing data errors complicating things.

I expect soundex would allow duplicates, because they sound correct. You want a way to prevent typos. When you let users type text you are going to get loads of errors. Something like 7mm will be entered as 7mm, 7 mm, 7m.m. and loads of other things. It's very hard to make anything foolproof.

I thought you said that the colour element of the openargs failed, and I thought it might be connected with the fact that openargs is a string. I have sometimes passed multiple openargs elements with a string separator, and parsed the string accordingly, but without using a class.

Might the data be there, but the button text colour is being changed to be the same as the button face, somehow? What do you see in properties, format that identifies the button. The numbers don't seem to be a button image that MS would provide?

In this sort of technical case,can you not control the permitted values by using a table of values, including the id of the user who created the value? Then the "genus name" or whatever in the "subject" entity becomes a numeric id, (referencing the permitted values table) and your problem...

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.