Search results

Having said that, you also have to realise that users are likely to be conditioned by their previous experience and won't necessarily recognize and value all improvements at first sight. The real problem is that developers understand development, but don't understand business practice, and the...

I still don't believe that any database needs to grow month after month, unless it is caused by normalisation issues, and duplication of processes. Therefore the ever expanding project could be dealt differently without needing to add new forms perpetually. Additionally, as already...

I'm not sure but you might also need spaces before and after the equals sign in these expressions. I probably add spaces in SQL expressions where I don't need them, but I know for sure there are some places where you do need to have them.

And you academically discussing a notional super sized project doesn't mean you really have one. I still don't understand why every month you need to redesign the project, unless it's not been well designed in the first place. That's why I would rather not discuss hypotheticals.

@amorosik I really think you are talking about an academic/esoteric situation that is most likely unable to ever arise. ie. Can you comprehend a system that is too big for access development? I just can't personally. I have systems that need more space for millions of records, but that's a...

Maybe I'm wrong. What I thought was it's possible to have one mdb that will run correctly in either bitness of access, but it won't compile to an mde that will do the same. That's what I meant anyway.

@Misionero I don't think you are getting this. This is two 1 to many relationships. Workers table Projects table WorkedBy table Workers 1 --- N WorkedBy N ---1 project. There is NO direct relationship between the workers table and the projects table. (Well, there's a M:N correspondence, but...

And the real question is .. why would you have a project that is never finished? Why would it need to grow continuously? Why can't you design a form or a query that works correctly in both 2024, and also runs in 2025 without needing to add a new form for 2025. I assume that's the sort of problem...

You can have conditional compiler directives something like this below (Offhand aircode) Others will know the precise syntax. The code will work correctly at run time, and resolve the bitness. The trouble is that you can't build this into an mde/accde and have it work in both bitnesses, as it...

If you do that you are back to the same issue. It's hard to develop new facilities as you are always working on the live database. If you split it you can develop using a test version of the database with a test version of the data. When the work is completed, you can release the test version...

If you use mdbs it's a lot easier. You can build with conditional options to select code that is compatible with A32 or A64 and have that resolved at run time. That won't compile to an mde, but it does mean you can have a single database that will work with both versions of access.

Seriously, I don't see how you can need over 1000 forms.

My recommendation is to understand the full scope of the project, and to get the data analysis correct, so the table design stands the test of time. Everything else flows from that. Edit. There is no real reason for a project to grow out of control. If you are adding lots of forms each month...

With this sort of thing, it's good if you can get a standard storage mechanism. Instead of using the parentheses, give the values a separate comma separator. So you get 2, part number 1, 6, part number 2, 8, part number 3 This way it probably becomes easier to process. You have to realise...

Office used to install as 32bit by default, but it's changed to installing as 64bit. You could reinstall as 32bit, and see if that fixes the FoxPro issue, but it does beg the question as to how your other databases are being used. If they are compiled to accde versions, then users might not be...

@Misionero What you will find is having lots of child tables can make database development awkward, and can affect performance in some ways. It makes a lot more sense now you explained what the DNI actually is. So one way is to have a person, and store the DNI details in the person table...

@GaP42 An interesting discussion on the peculiar nature that a "simple" address can become in certain cases. Out of interest where do old passwords get stored. Is there a long encrypted string of them all somewhere? It has to be stored somewhere, and it's really representative of a 1:N...

@Misionero Your original.premise is wrong. It's wrong to say a person can have just one document. A document might belong to one person, but a person can definitely have more than one document. In point of fact a document can have more than one owner. A deed for a property can have multiple...

A person table linked to an identification document is 1 to many. Let's say you store a passport document. Now if you replace the passport you can store both the original passport and the new passport. You may need the old passport reference. It's not changed from 1:1 to 1:many. It's always...

Well then you are ok to enter more, aren't you?