Search results

first of all use Dim not Private (Dim boolVar As Boolean). second , without going through the hassel of explaining why .. put ur varriable declaration statment above Option Explicit line then add an Option Explicit one above it (now u have 2 of it) , then remove the lower Option Explicit .

Your function is working fine here , would u post the syntax u run ur function with ? :)

datAdrenaline i love it when people enterpret my words in a professional manner and take all the credit :D

waiting in anticipation then ;)

another hint ArgID might be numeric , so remove the single quotes , yet we'll never know he never posted the table structure :)

Chris for a peculier reason MS Access hates arrays , and yes i was at ur shoes one day , those who posted that solution never realy tried it or probably has add loads of ms libraries to their project referances :) All you have to do is strike out the As statment so it goes like : Dim...

For your eyes only here are two neat tricks : 1 - Right Click your report > Sorting and Grouping > select EmployeeID in Field / Expression > Select Yes in Group Footer Now in EmployeeID footer add a text field where its Control Source property has the value : =Count(*) 2 - Add a text field...

man access can get wiered on me :)

your question is similler to : I wanna shave , does anyone know of any good movie i can shave with ? first of all memo fields are hidious fields that have loads of problems in dealing with. (You cant use a where condition on a memo field) second if you have the same data stored in other...

i wonder how it worked over ms access 2003 :p

You are trying to overwrite not reopen ,windows usually lock opened files (not unless it was one of those buffer/hash technique projects which are not our case) so it wouldnt be possible to overwrite which unless windows release the lock by closeing which:)

now this proves my theory, nobody knows ado and its all about tailoring heritage of ms access 97 dao scripts. Best regards and sorrow yves

nosurlien , please note that : DoCmd.OpenReport "invoice", acViewNormal, "Main", "[contract number]=" & Forms!Main![Contract Number] syntax mean the following : "invoice" : report name acViewNormal : report to open in print state "Main" : filter similer to where condition , ie...

the error was probably a result of another issue (repetitions , invalid charachters , blas blas) but realy its not a problem to keep both the same name , i use it all the time and it saves me the hassel of haveing to track multiple names for the same field.

it realy wouldnt matter if field names and control names collide :) however yes spaces are not recommended in nameings meanwhile i have seen bizillion users posting sources utilizing it (spaced names) to the extreme so i'm becoming to think of it as a norm :)

now please oh please note the following , stSQL1 also will fail , only its condition havent been met yet :)

You supply Main as a filter field , filter to what exactly ? just remove it or make sure main is selected as a record source if Main was a table assumingly present on your database Now i wonder if MS Access 2000 didnt find a bug in there :)

heh just copy and paste "Type of Premium" to Name field please :)

heh .

that project is big but here are your hints 1 - Your table2 should only have a serial indented key (Autonumber field) as its primary key and all fields should allow duplicates 2 - Use after insert in forms operating on table1 to always keep a copy of inserted records as a fresh start in your...