Search results

I don't quite understand the concept you're reaching for. How, in SQL Server, would you have a temporary view? They don't exist. What you do have are derived tables, subqueries. i.e. inline SQL statements. That's what you had in code surely. Building up the SQL statement - you can then use it...

Declaring the parameter (and it's data type) is usually enough for the value recognition issue. (But Eval works too - it just doesn't feel as "pure" to me, but it feels more so to others - you choose :-) The wilcard can be made consistent if you are willing to switch operator. The Alike...

Well, you are already using DAO, but you are indeed trying to open a connection to the currently running MDB/ACCDB? As mentioned - splitting in Access massively often involves maintaining linked table to the back end (there's almost no reason not to). Those links facilitate data access very...

The problem is almost certainly that this really is the SQL definition of your QueryDef. When Access opens a query in design view, it re-parses it. The QBE is a wonderful thing - SQL Server more or less copied it conceptually for View creation back in SQL Server 7. But it works as all computer...

Glad you're sorted. Yes, they really don't have a choice - the tables sourced in the FROM clause are the only ones available for selection and you can reference them by just the table name. However with more than one table I prefer to alias them anyway (both for brevity and precision). My...

I think there's a discrepency between what you're attempting and what you want. But that involves knowing what you want. ;-) What my guess is that you want: You have a running application and you want an Access Form, Report or Datasheet (yek) to open to display results of a crosstab query...

Glad it's sorted. Just a couple of points. :-) Certainly Indexes would have been the most important consideration to address. Thankfully they have been. Jet itself does tend to better optimise ANSI joins to Non-ANSI (also known as Theta) joins. i.e. in the FROM clause rather than WHERE...

Well, I'm glad that you achieved it. Not that it affects my ability to envisage the intent. I'm sure it's just spiffing though. Cheers

You do indeed need to specify the index to use. Since Rob's example code already included that, I mentioned it only in the context that FindFirst and Find don't need it ;-).

I'm afraid I'm just not seeing the UI effect you're trying to achieve at all.

Just to be clear, the AfterUpdate event will always be raised. You need to make a decision based on the NewRecord property in that Event Procedure. It could just be to execute the code or not - and let AfterInsert handle new records. But the event (and hence the associated Event Procedure) will...

Sounds like the Click event to me!

You can use the Seek method on any recordset which supports it. In DAO this means that the recordset must be a dbOpenTable type. This would indeed usually mean a non-linked table. But you can, of course, open a database object to the MDB/ACCDB in question and then a table type recordset on that...

Well all object variables are just pointers to the objects themselves in memory - created by the components of the library in question. Yes, a static ADO recordset (that's the biggest difference of data location) places a heavier client-side memory burden - but that is really the...

Not quite the can of worms it could have been - but unsurprising to see it echo on none the less. :-) I think a lot of what I have to say on the use of the Close method has already been said in this thread here, from a while back. So I'll try to avoid repeating it here. There are occasions to...

Hi This does come up from time to time - and it's not a hard and fast answer. Have a look at some existing threads. http://www.utteraccess.com/forum/Testing-DAO-Recordset-Ope-t1946173.html Which links to the more directly applicable...

Wouldn't that be Jaaaaazz... niiiice! (For those unfamilar with the Fast Show http://www.youtube.com/watch?v=MsQYzpOHpik) Welcome!

By >> copying the SQL into the VBA recordset do you mean hard coding the SQL in VBA and opening a recordset based on that? If you're duplicating the query definition in code then, IMO, that hard coded VBA string is limiting you as opposed to using a dedicated, reusable query object. There's no...

Yes, exactly. VBA is single threaded and to perform asyncrhonous downloads in the XML OM is more hit and miss in my experience (though I've played with it too).

With a function such as fHTTPDownload below. If it fails (returns False) the download didn't work - you can explicitly check for the file afterwards too of course with a simple Dir function check. (See the VBA Help for more on that if need be). Importing could also use a built in method (note...