Search results

i have a very complex claim sheet i'm trying to code.... i want the code as efficient as i can so i'm trying to make a routine that does all the work for each line that i can re-use. to do this i REALLY need to be able to pass names for controls and fields as variables (this never seems to work...

fair enough; to be honest I'm not positive how it will work. i'm trying hard to figure out ways to do what we need. tragically i've come to accept that we simply HAVE to pause the program and let the user do his thing in excel (its a claim sheet) and the problem is each one is unique... i need...

i'm just not familiar with the excel event model to know exactly how to get it to "pass" back those variables.... any good web sites you would recommend?

i've linked data from excel spreadsheets often to my database; wondering if there is any way to pause for user input? i need to open the sheet and have the user select a cell or 2; the spreadsheets are dynamic and no way to predict which cell the data will be in.

LMAO. for the love of god. stop selling yourself short. u just solved it here; thanks man. i used Eval(Forms!FormName.ControlName) instead of Eval('Forms!FormName.ControlName') so thanks for that extra 2 cents input it help heaps more than u thought it would!!! Cheers man.

ok it's def the query as other queries work in there; the query does load a parameter from the form on load but thats not uncommon; i've never had to worry about that before. i don't pass a parameter to the variable, it's self filtering. i've tested at the load point and it work fine, doesn't...

seems to be implying i need to use a querydef statement to open it? i can't believe thats true i've never needed on just to open a recordset before.... if what i'm having trouble with is definitely: Set rstClaimsAndVaries = CurrentDb.OpenRecordset("qryCurrentVariation") (and this baffles me...

to make life easier i've reduced the error section down to this Public Sub testdao() Dim rstClaimsAndVaries As DAO.Recordset Set rstClaimsAndVaries = CurrentDb.OpenRecordset("qryCurrentVariation") If IsNull(rstClaimsAndVaries!LodgeAttempts) Then rstClaimsAndVaries.Edit...

anyone see a problem with this: Dim rstClaimsAndVaries As DAO.Recordset Set rstClaimsAndVaries = CurrentDb.OpenRecordset("qryCurrentVariation") ???? i use it all over and just got an error: "Error Type: Too few parameters. Expected 1" its part of the code below; when i go to debug it...

i'm an ass. please disregard this entire post!!! *soooo stupid i am...*

for the record the code under where it halts is untested and prob not entirely right. feel free to comment on it too if ya like :) thanks.

ok. i have code doing lots of stuff, i've include the offending script to be as clear as possible. Here is the problem: code comes up with an error: "Error Type: Update or CancelUpdate without AddNew or Edit" Prob is i'm NOT UPDATING A RECORDSET!! and it doesn't stop and debug i had to step...

Really??? i was sure it was a new 2010 feature. wish i had known that sooner. thanks.

i know this is a new feature in 2010; the help files don't seem to detail it at all. anyone here have any experience yet automating the pdf export from vba? i'm sure its not that hard, just haven't done it yet. thanks guys as always :)

fair enough!!! seems crazy but i hear ya - assumptions and microsoft go together like whisky and guns... cheers!

thanks thats very helpful. the whole point of the entryID was to have a Unique identifier that works in outlook and access. ie. the user adds 2 emails to the directory that they added to from before. i need to know that we don't re-import the same email again and again. so SURELY (LOL!!!)...

i thought so too. really need to stare at this screen a bit less lol...

ok i admit blatant ignorance....WTH else would be in there???

LMAO!!!! i was wondering how he thought an insert statement would help, didn't want to say anything. totally failed to notice the .Execute instead of the .RunSQL !!! *runs off to make some more coffee* lol. thanks for the pointer...

yeah slipping this in worked too Do Until TempRst.EOF With TempRst .Delete .MoveNext End With Loop TempRst.MoveFirst but wondered if it could be suppressed within the .runSQL statement itself.