Search results

So how do I do what I'm trying to do? I can modify the query using the RecordSource property of the subform, but I have to give the subform some default sourceobject or the attempt to update the RecordSource claims the subform doesn't even exist. If I do put a query as the SourceObject, then I...

I have a form. In this form I have a subform. The subform is not any specific form. I just clicked the subform tool and drew a subform. Then in my code I'm trying to change the source object of the subform to a dynamically generated query. I can easily do: Me.child8.SourceObject =...

Resolved. stupid mistake on my part. I changed the table that looks up the data's type to a memo. The table that the control was actually bound to was still text though. Once I changed that I was fine. Thanks for the help

I have a field on a form. This field gets automatically updated by an event. Sometimes if the text attempting to be put into the control is long (example: length=249), it gives an error that the data is too long. I searched in the properties for the control and couldn't find anything that...

Resolved I was referencing my subform by the name of the form instead of the name of the instance of the form as a subform. Aka, it may be frmDepartments, but when it was created as a subform on frmCompanies, that subform's name was Child3. =RowNum([Forms]![frmCompanies]![Child3].Form) worked...

The textbox just displays #Name? I don't know what this error means but it seems to me that it isn't even calling the function at all.

I just want one for GUI reasons. I'm trying to figure out why this example isn't working. But did.. then stopped working. worked on my test forms that were linked the same way.. and won't work on the original forms.

I tried =RowNum(Forms!frmCompanies!frmDepartments.Form) and it worked. Why? I don't understand why putting Form at the end makes it work. Update: Now it's not working that way. It did, then I copied it form my test forms into my main forms, it didn't work there. And it stopped working in the...

I have an Access 2003 form (frmCompanies) with a continuous sub-form (frmDepartments) I need a row number (sequential: 1, 2, 3, etc.) for each record displayed int he continuous form. I have found an example of how to do this online but it is not working for me...

Yeah and that's fine. There is currently no lower level entity than a department. (this app doesn't actually concern companies or departments. those are just placeholders for what the app really covers that i used for the sake of asking this question. what it actually does, i can't discuss due...

I want all department records visible at once, one after another, vertically. So is the way I found to do it correct then?

I think you may be suggesting this because I didn't explain what I"m trying to do very well. A company may have multiple departments. And as soon as they start entering information for one department (HR for example), then another set of fields will activate so they can enter yet another...

The table structure you described is exactly what I'm using. All I'm concerned with at this point is getting the form to work in a certain way. Is the normal solution for something like this to have the form be tied to the company table and that form have a subform that is both "continuous"...

I have a form with company level information. At the bottom of the form I would like to have a subform (or just a set of input boxes) that contain information about a department. And when they start entering information into one of the department level fields, another subform (or set of input...

I have an access application that has a front-end component which the users use to find the factorials/exponents/products of numbers with large amounts of digits. I came up with a better algorithm (which turned out to be a known way) for computing factorials than the recursive: factorial(n) = n...

In an Access Query, which is applied first: Grouping or Criteria? I am trying to run a query whose results could potentially differ depending on whether the query's data set is grouped, then filtered based on criteria or filtered based on criteria, then grouped. (i've done a little testing and...

I have no control over or access to the structure of this database. It's not even based in my state. It's a large corporate database. I agree that the table structure is absurd and as a result, a pain to work with.

Well tests show that the amount of time this query takes to run isn't dependent on the number of records in the local table. So I'm guessing the "forever to run" is just the initial evaluation of the pass-through query. And I'm guessing the reason the pass-through query runs so quickly on its...

So here's my setup. We have a database with several tables that have over 255 fields. So we must use pass-through queries to access some of the data. Usually no problem. Here is my pass-through query: qry001: SELECT db001.table001.field001 from db001.table001 If I execute this, it instantly...

Yep. And in the end I found a way around this issue: polar form. I'm utilizing the Box-Muller method for getting random variables (monte carlo style) but by converting to polar, I get rid of a trig calculation. One less precision-killing operation resulted in yielding values roughly one...