Search results

This problem has been plauging me for the last few months. I have an Access ADP application connecting to a SQL Server 2005 database. I have a continous form. My goal is when I open the form, I want to build my own stored procedure call, with parameters that I determine and provide in VBA code...

So is editing with conditional formatting not possible?

Actually, the problem was that my textbox was named the same as the control source. I'm almost there now. New problem is that the field isn't editable after formatting.

First I tried it with something simpler: =IIf(1=1,[amount],55) I get an error "Circular reference".

Thanks Paul - where does this go though? In the Format property, or the control source? I couldn't get it to work in either. I'm going to try playing with it in the VB. Also this is a continuous form. Will it work properly? I want something like: Amount -------- 45% 67% $500,00.00 87%

I have a feeling this maybe can't be done but figured I'd give it a shot anywa. I have a table which has an "amount" column. That column can either hold a percentage value, or a dollar amount. I'd like to be able to approrpriately format the number in my forms depending on the type. So...

This is terrible. I'm quickly learning that continuous forms are a major pain in the ass! Does this mean that there is no way in Access to single out a specific control in a specific record on a continous form? There must be something like Me.cmdAmount(2).value = 50 ?

Bob - this solution looks good but would it work on a continous form? I'm not sure how to code control references in this case. I'm doing something similar in a form that looks like this: Percent Amount ------- -------- 1 45 .5 70 .5 80 When someone...

Gotcha. But how do you create the form to begin with? I don't want to hardcode all the expense types on the form because the user can add new types. That's in a lookup table. I need to somehow dynamically create this form.

You guys helped me through another problem I was having so I thought I'd throw one more challange out there! I want to have a form that is sort of dynamically built and has placeholders for data, even if the rows are not there yet. Here's an example of what I mean: I have two tables...

Also - one more question: How would someone accomplish this? I have fields in my table that represent percentages - they are decimal data types in SQL Server. When I display them on my forms though, I them shown *100. In other words in the database the number would be stored as .5 but I want it...

I've had some success but I've had to change the way I think about my forms to fit more inline with the Access way of doing things. I'm still having problems though - now using stored procedures that have parameters on my form. I have one that populates the form itself, and then another...

Thanks RG. I'm going to try this. Actually, it may be even better because then I can maybe do the actual INSERT in a stored procedure. The issue then is - will the recordset automatically update, or do I have to somehow refresh it and reset the cursor to the last row? You guys are very helpful...

I want to, and am enforcing it in SQL Server. Problem is that it doesn't seem like the SQL error is propagating up from the database to my application.

I figured it out. A FK violation was being triggered behind the scenes. When I deleted this record in query view, the error message came through. Now this leads me to another question (or two): 1) How can I get the SQL FK Violation message to propagate up to my form? 2) This is why I like to...

I don't have any other code other than one Sub which contains the one line for delete.

What type of error handling do you mean exactly? I can see the error being returned by VB. It's Run-Time error '2501'. Is there someting I can do to get more information on the error?

I can delete directly in the query. I can also delete using the in-form row selector. When I add my own button though, I get those errors. I've reduced my code down to nothing more than one line: RunCommand adCmdDeleteRecord. Gives me the regular delete warning, then the error I described. This...

Thanks for the reply RG. I was just planning on having most of my business logic in stored procedures rather than in the application itself. Maybe this is not the Access way of doing things. I'm trying to get around it now and am binding my forms to queries, etc. I don't see the advantage to...

Hi – I’m an experienced SQL Server and web programmer but don’t have too much experience programming in Access. For the current project I’m working on, using Access was a requirement. As I begin, I’m starting to think that maybe the way I’m approaching the design of my application isn’t really...