Search results

Easily done my friend, but at least your loins are OK

Just and idea since you're using reserved words. Would it be that you need to explicitly declare the variables. It's the case in queries that don't have definite headers such a cross-tab queries but may also be the case here. Just a shot in the dark but try setting the variables in the...

Ah ha, reading it again I see that's exactly what Mark meant. Sorry combinations of late night and square eyes. Thanks

Many thanks for that, I always thought the opposite was true, but will have a quick read-up in the morning. Ta

Just writing some queries for 500K + records with a various restrictions in the WHERE clause and was wondering if the order in which I restricted the data would have any affect on query performance. Is it better to place the broadest restriction first and then filter down form there or does it...

Can't open your images.

Nice Spot, I'm gonna give you a thumbs up too

or even Nz(DLookup("[technologia]", "tblDolZlecenia", "[Id_zlecenia]=" & Forms![frmZlecenieMarzena]![ID_Zlecenia] & " And [technologia] = 1"), 0)

Really glad it worked out for you Take care

The easiest way is to do this is through a query otherwise you'll have to iterate through the rows in the listbox (I suspect much of the SQL for the query is already held in your Listbox) and a query will help you better visulise your data. Create the query first in the Query Designer so can...

Sorry missed the bit about all items in the list box. Isn't ID_Zlecenia unique?

Couple of ways to do this, but without knowing much more what about If DLookup("[Prioryte]", "tblZlecenia ", "[ID_Zlecenia]=" & Me.Lista0) <> 7 Then Msgbox "This is Not 7" END IF of course you can replace Msgbox "This is Not 7" With your update code try it on the AfterUpdate Event of the...

Sorry I cut my reply off a little short- got called away I meant top point out that this isn't a very good method as people have a habit of clicking a list box and in this case it'll change your recode every time it's clicked without warning. Of you must do it this way then perhaps a message...

Assuming that the list box is bound to Priorytet what about a simple If Me.Lista0 <> 7 THEN so something - Like run your update query END IF Also if you're always changing tblZlecenia.priorytet to 7 you don't need " & "7" & " - a 7 without the ampersands and quotes will do just fine...

Hi Do you mean you want to UPDATE (Change) Priorytet in tblZlecenia to 7 for whatever record is selected in your Lista0 Or Do you you want to Just check if the selected record in your Lista0 is ALDREADY 7 Perhaps it might be better if you explain what your're trying to achieve Take care...

how do hide the password? - Hope that didn't strain you too much

Here's a scenario I connect to BE SQL server with large tables and to avoid continuous hits to the server and reduce network traffic and most importantly keep the network guys off my back, pull records that are accessed frequently down to temp tables in a locally held access BE (ACCDB) which is...

Pat, Just read your post - very informative and nicely written Just out on interest is Access 2007 onwards still using an mdw?

Hi Interesting point about excel. However, my client needs are quite simple, nothing more than adding pounds and pence so 2 decimal places sufficed. Perhaps down the line I'll come up against a division or % but even then the margin of error wont be overly significant, a 100th works fine for...

I've come to the conclusion (rightly or wrongly) that the Money datatype in sql server is pretty useless when it comes to compatibility with access Currency datatype. In the end I gave up trying to make it work so have converted the server datatype to decimal and left the temp tables columns in...