Case Sensitive VBA Query (yet another)

[SorenIX]

It's definitely worth investing some time in your table design before you get too far. Might be worth creating a new post under the "Theory and Practice of database design folder" and describe your business model in English terms. Also consider posting your d/b with sample data.

Hopefully someone can provide some good links on relational database design. You can of course google but I found that some tend to be better than others at explaining the main principles.

I will look into this.

For now I would like to fix my case sensitivity problem. I'll get working on it tomorrow I think. I was working on another problem at the same time on another thread. It seems to be fixed.

 

[SorenIX]

It's definitely worth investing some time in your table design before you get too far. Might be worth creating a new post under the "Theory and Practice of database design folder" and describe your business model in English terms. Also consider posting your d/b with sample data.

Hopefully someone can provide some good links on relational database design. You can of course google but I found that some tend to be better than others at explaining the main principles.

I looked into the relational stuff and it's hardly applying to my database. I guess this is why I didn't think about it before. The reason is that it's an application that is not the main database. Let me explain myself.

We've got a web application that stores the same kind of information on a server. That is the true and real database people go look into for information.

My application/form/database is just a tool. Directly on the web application I mentionned above, it is impossible to manually do massive information update. The only way to do it massively is by sending an excel file to the managers of this application and they will then do a massive import in the web database. Other than that you have to load the pages one by one to access the record and click another time to edit it. Many loadings.

To put it simply, the informations that comes into my database come from this server database, and the information isn't always keeping its integrity as people from around the company manualy enters (sometime) random values.

Now you might say it's kinda pointless to developpe a tool for this, but know that I'm working on making the output of my database workout with the server database. One of the main reason why this tool is useful is because it's much much much much much faster than the web application and we have times of the year when we need to rush the information into the server database.

So I've pretty much explained it.


On the side line, I'm still looking into that Case Sensitive problem, haven't really figure it out yet.

 

[Pat Hartman]

Excuse me while I indulge in a little personal chuckle. I don't understand who decided that every application needed to be web based. There seems to be some pervasive thinking that if it's "new" it's "better" and that's why I say that the inmates are running the asylum. Call me old-fashioned but I believe in efficiency and value. Choose the correct tool to achieve your goal.

@SorinIX, We are 22 posts into this and I still don't understand your case problem. Queries maintain the case of the text strings they work with and the only time case is an issue is if you want to see only the records with last name = "smith" and do not want to see "Smith".

If you want to do case sensitive bulk updates, so that you replace all instances of "smith" with "Smith", then use the find and replace feature. It IS case sensitive if you tell it to be.

 

[SorenIX]

There's a little more story to it, but this is not the matter.

I'll try something right now. Give me a few minutes.

 

[David R]

It's definitely worth investing some time in your table design before you get too far.

This is an important piece that you're blowing right past. "Relational doesn't apply" is hogwash.

Most of your difficulty here is coming from your non-relational setup.

 

[SorenIX]

This is an important piece that you're blowing right past. "Relational doesn't apply" is hogwash.

Most of your difficulty here is coming from your non-relational setup.

No, it comes from my application not being syncronised with the server database.

 

[David R]

Wait, what happened to

There is no server, the database is local.

 

[SorenIX]

I've explained it above.

We've got a web application that stores the same kind of information on a server. That is the true and real database people go look into for information.

My application/form/database is just a tool. Directly on the web application I mentionned above, it is impossible to manually do massive information update. The only way to do it massively is by sending an excel file to the managers of this application and they will then do a massive import in the web database. Other than that you have to load the pages one by one to access the record and click another time to edit it. Many loadings.

To put it simply, the informations that comes into my database come from this server database, and the information isn't always keeping its integrity as people from around the company manualy enters (sometime) random values.