Search results

I don't agree , i agree with post #6

I have the same problem If IsNull(Me.Reason) Or Me.Reason = "" Then MsgBox "You must set reason for termination first!" Exit Sub End If This doesn't work? I have found replacing all uses of IsNull or = "" with If nz(Me.Reason,"") = "" Then MsgBox "You must set reason for...

I can see I have a lot to learn :confused: Thanks for the info.

But your saying that an entire update fails? what if the previous change was against one specific field, but the new changed change more than one field, so we want to keep the first change to the one field while applying all other changes except the change to that specific field changed...

Well so far using an SP is proving fruitless, the whle app grinds to a halt. The old 'bound' method via a normal query against a linked table view takes 1-2 seconds to perform a filter, via SP it takes 58 seconds :eek: I'm not sure also I want to dive straight into a dicconected model type...

I seem to be going round in circles trying to hide the main DB background so only the open form is showing. Can this be done? I've unticked every single option on Options -> Current Database I've made ALL my forms popup, i've packaged it into a runtime. Nothing will make that darn...

Thanks guys. I am starting to find that triggers/SP's should only be used where appropriate. I tried to bind an SP to my form and the app ground to a halt! I certainly think string concatenation on the client side for basic GUI view updates, is better than SQL data transfer! Also storing...

Thanks for the reply. I changed one of my apps yesterday to bind a form to a passthrough query and executed a stored procedure and it ground to a halt! So no i need to know when using an SP is better and when it isn't. A little investigation says when you are returing many records in a...

ok, found you need to create a passthrough query with an embeded connection string. In the query you write EXEC sp_stored_procedure And then it will grind your application to a halt, even just trying to navigate around in 'develop' mode will have your db locking up, egg timing and basically...

How do I set my stored procedure as the record source to a form? Where is my stored procedure listed so I can select it as the source? Thanks, 1DMF.

ok, didn't realise I had to execute it to create it, i thought saving it would create it.

I've opened up SQL2005, under 'programmability' -> 'stored procedures' , I right click and select 'New Stored Procedure' , I create my procedure. I close the window, it asks if i want to save, I say yes, give it a name, click save... Now what? where is my SP?

I'm glad I'm not the only one pondering these questions when using a SQL backend with Access. Hopefully I have come to the right place! I am curious regarding triggers as i have been told that you shouldn't actually use them as they slow things down. Is this the case? Also in the example...

Hi, I moved to a SQL backend many years ago, and all has worked well, however, I have been made to feel like an idiot and a total novice, because I know nothing of stored procedures/ triggers / transactions etc.(well I never got any training, so it's been a seat of the pants job working here!)...