Search results

I think the default is to not trust objects, but surely the user can elect to trust them, or set trust centre properties to trust them.

This has probably been stated, but "0049" is a text string, not a number filled with leading zeros. I doubt you need to manipulate it as a number. If it's a text string then values 0049, 049 and 49 are different and not equivalent, which may be important in your system.

If the breaks are quarter hours, and the project is whole hours, I don't see how you can have 40 minutes in the answer. The answer would have to be at a quarter hour point.

If you want to delete records you have to think carefully. If table A is 1 to many with table B, and tableB is 1 to many with table C, then you can't delete a record from table A or B, if it would leave an orphan in the subsidiary table. So you need to be careful if you allow cascade...

Just a thought. There was a thread recently about text conversions, that highlighted that VBA strings are different to some other strings. It might be that vba is causing the errors by the way it treats the strings. I'm not sure how to explain this in technical language, but it might offer an...

In 32 bit access the biggest long integer is 2billion roughly. Your numbers are bigger than that and won't fit, so they represented as exponential approximations. You could show them as text strings, but then not manipulate them as numbers. In 64 bit access, there's a bigger date type, a long...

You have two nuanced options. The problem with running it as a query (open query) is it will run and just report the number of failing rows, which may be dangerous, as it's hard to see what it actually did after the event. If you execute it, you can trap errors so if it rejects some rows, it...

As I said, there's something In some text fields that the import wizard doesn't like. If you can identify the rows that fail you might be able to see the issue by inspection. Depends how many records you need to check.

That error is always symptomatic of a data corruption to me. Maybe the data in the import file is badly formed, so that certain rows can't be split into fields correctly. What are you trying to do with the data? Import to a new table or to an existing table?

That's a good point. A list box/combo box is generally pre-designed to sort the data alphabetically to facilitate finding the entry you want. Generally the query used to fill the box ought to try to restrict the number of rows returned to a modest number. If you want to search data generally...

What I found was that the A2003 menu (and the A97 menu) was/is a dream to use. It uses a very simple process to successively show user designed pages of menus. You design numbered pages, so page 1 may have say 10 options* The default was 7, I think, but I ended up having 25 options, 3 columns...

@KitaYama I think that's just semantics. A navigation system of any sort is equivalent to a menu, and a large system just cannot display every option at the same time, so you need a way to drill down through the options. If you add combo boxes you need to work out how and where to display and...

Well, I think they can be reached easily in a menu system, but you can't see everything at the same time. For example, I built an enormous sales order processing system with hundreds of forms. If somebody wanted to enter a sales order they didn't need to be looking at the product and sales...

I find the ribbon issue is that the icons are just too big. A drop down menu was a few pixels high to start off. Dropping down a 10 option menu only used a little screen space. How do you provide a sub ribbon, and how many options can it contain. Is it a vertical structure, or another...

I don't know about that. I just think A97 and then A2003 were very mature and you could whatever you wanted with them, pretty much. Later versions added in new features such as formatted text boxes, form control anchoring, new ribbons instead of menus. I doubt there is any way that later...

You shouldn't need to add notes like that. If you keep a record of receipts in another table, then you can store the receiptID against all the invoices that were paid by that remittance. All you then need is the date and amount and customer in the receipts table. If you have some invoices that...

@The_Doc_Man Yes that's I meant. Similar issue tracing the owner, but not quite as critical because you can save a different filename, although then you would have problems joining all the edits together if necessary. I can't remember having had excel issues though. I assume users know better...

If you still have the original license key, and install disks, I'm pretty sure you could reinstall and activate the software. It's easier for MS to allow a few repeat uses of keys than police the system to that extent.

Don't excel power users have the same issue. They get "another user has your file open. Do you want to open it read only?" Don't they have the same issues determining who has opened the spreadsheet?

Yes, so the programmer who looks after Access asks the system administrator to sort it out. The programmer might be the sysadmin. What you do need is to understand what's causing the problem and how to resolve it, which a general user won't. And the users need some general education. Many...