Recent content by tylersontag

Well, i ended up biting the bullet and pulling the form code out and placing it in the backend VBA code. But setting the RecordSource directly to the form was killing performance... 8 or 9 seconds load time on the page comming up... So i experimented with setting the Form.Recordset directly...

Yes, that is the way I would have done it if I would have writen it in the first place... sadly this is not the case. I had considered the rewrite, but only as a last result. It would require 3 extra queries not to mention the multistep transformation of the results into its final value. So...

Alright, take a shot at this one. I have a form; it opens up another form, and let’s calls it the Report form. The report form has 3 embedded sub-forms. I'm trying to read a summation value in the footer section of each one of these subforms. The problem is that it takes about half a...

Works like a charm (with wscript and cscript) changing the object to Create rather than Get. Thanks all!

Hey all, I've made a macro that automates a load process and i'm trying to figure out a way to automate the running of this macro :-) I've been working with a VBS file, but not with much luck. Its pretty barebone: strFile = "C:\MDB_file_Path\MDB_File.mdb" Set objAccess =...

Looks like its working, thanks!

I have a vb script that opens my MDB with a command line argument to run the "AutoLoad" macro The "AutoLoad" macro simply does a RunCode pointing the the "Auto_Load" function within one of my Modules. (Brickwall)In this function, i'd like to call and run some existing code behind one of my...

Sure could, so what would be the syntax to open a form from a module? Then would i just pass a parameter or a condition to tell it to run my specific "AutoLoad" function?

I'm wanting to automate a process, so concurrent to the normal execution of a form (Open another form, prompt questions, display stuff, comit changes... etc) i've made a Function that calls existing functions behind the form and automates the responces to bypass the need to have a user actually...

Figured it out, it was the form open 'whereas' condition... its always fun fixing someone else's code who doesn't comment things... Why populate fields based on all 10 values extracted from a file when you could simply use 9 of them and substitute a syntactically correct but totally different...

bump? Any ideas?

Hmmm.... the actual change simply went from: For every column (i) in table: (ADO) tblsNewRow(i) = value to... (Exec) insertStatement += ". ' " + value + " ' " next So its essentially building the new rows the same way.... The error occurs on the code behind a form...

Yes, that is what i meant, i suppose i didn't know how to phrase it properly.

I recently migrated some backend data from a local access MDB to SQL Server. Because of the use of link tables, the existing ADO style updates were horribly slow. So I swapped out the code for DAO and reduced the insert time from 11 seconds to less than one. However, later in the execution...

Thanks, looking at each element of the DAO error solved the problem (though i couldn't get any debug window to pop up...) of the 3 errors thrown the first one was an integrety constraint, a field that had been an autonumber field was now just a non-null field i was not filling out on my insert...