Use ADO with Parameters

Yep. It might be better to post what you have so far. I'm assuming this is a stored procedure in something like SQL server?

It's an access query, I can post the SQL for the access query, or would you rather see the VBA from Excel?

Both please

Hmmm...Thank you for the response. I will look into the Database Design and Normalization. The more I think about it, I am running the same query from in multiple databases (because the data is being pulled from different tables). It would almost be more feasible to me, to just run a Union Query so that way I am only entering one database, and running one query, as opposed to many.

I am running the same query from in multiple databases (because the data is being pulled from different tables)

Do you mean that you have the same table layout in multiple tables in one database, or the same table layout in multiple tables in multiple databases?

This seems very wrong. For example, you shouldn't be repeating customer details address etc for multiple orders. You should have at the very least, a customers table and an orders table. The Primary Key in the customers table should be a foreign key in the orders table. Depending on your data, you may also want further tables for state etc.

The reason for this: If a customer's name changes/address changes, you only need to update the customers table once and this will cascade through, in your current format you would need to update the customer multiple times - this would be a nightmare. In addition how would you handle multiple contacts from the same customer - this may/may not be an issue depending on what you are doing.

Hope this helps

Thanks Rory

Oh I completely agree, the structure and layout is atrocious! The primary key that is assigned in each database is an auto number field, so the primary key really doesn't benefit the table either. I am taking this over from someone else who had it set up this way.. The set-up of this is SOOOO flawed, and I am trying to combine as much as possible. The status quo is there are multiple databases, with multiple tables, each containing orders, and customer info. Why? I have NO idea, but they are bound to multiple reports/forms that I haven't had the time to decipher through yet. So I was currently just running the query from each individual database (hence I made the Union Query). Another for the moment fix, I was thinking about doing was just creating a table in the databases, and just running a append query from each databases to the table I made so that way I am querying ONE table.

haha sounds like fun

Wherever I've worked, I've often thought that much of the complexity and illogical structure of End-User Computing applications was down to the incumbent ensuring his/her own job security. A little knowledge is a dangerous thing.

I know I'm guilty of that too

Originally Posted by Firefly2012

I know I'm guilty of that too

I've often time's complained about a programmer or contractor over-complicating a system, so that you have to consistently use them for add-ons, mod's etc. In this instance, I pray that it wasn't a programmer trying to over complicate things, it more-so looks to me like it was someone who didn't have a clue what they were doing.

Originally Posted by OnErrorGoto0

IME, 80% of it is down to the complexity and illogical structure of End-Users...

Stoopidity might play a significant part too - oh, and the need to hang around on web forums answering questions rather than doing work Hmm, let me see, that error goes away if I put On Error Resume Next at the top of the routine...

haha anything like this? http://thc.org/root/phun/unmaintain.html

Originally Posted by Kyle123

haha anything like this? http://thc.org/root/phun/unmaintain.html

That website is hilarious!!! OMG, I am passing along to all my programmer co-workers!

Access Denied for me Damn workplace...

Yeah I can't get on it either, but I remember reading it. It's brilliant, even worth reading at home

I will spend my afternoon doing this:
Dummy Interfaces
Write an empty interface called something like "WrittenByMe", and make all of your classes implement it. Then, write wrapper classes for any of Java's built-in classes that you use. The idea is to make sure that every single object in your program implements this interface. Finally, write all methods so that both their arguments and return types are WrittenByMe. This makes it nearly impossible to figure out what some methods do, and introduces all sorts of entertaining casting requirements. For a further extension, have each team member have his/her own personal interface (e.g., WrittenByJoe); any class worked on by a programmer gets to implement his/her interface. You can then arbitrary refer to objects by any one of a large number of meaningless interfaces!