Search results

Make sure that the property ColumCount (on the format tab) is 3 set the column width property to: 0;0;5cm to hide the keys. JR

Woulden a parameter query do the trick: PARAMETERS StartDate DateTime; SELECT * FROM MyTable WHERE MyDateField Between [StartDate] And [StartDate]+5; JR

No problem JR

stAppName = CurrentProject.Path & "\plat_blit_new.exe " JR

Try this in your macro: Attached is the shipping report for & " " & Weekdayname(Weekday(Date())) & " " & Date() or Attached is the shipping report for & " " & Format(Date(),"dddd") & " " & Date() JR

Then remove the underscore from your second Dlookup =DLookUp("[SCF ID]","tblCustomers","[ID] =" & [Forms]![EnterNewTransaction]![ID]) JR

Might be because Transaction is a SQL reserved word, try wrapping it in square brackets. myCommand.CommandText = "INSERT INTO [Transaction] ([TrxNumber],[CustomerID],[MovieID]) VALUES (" & T & ", " & C & ", " & M & ")" also sql is picky about spaces around keywords. JR

Attached is a very basic sample of the consept in the link I gave. -Unzip the folder to C:\ -Open the MyFrontEnd.accdb (access 2010) -Try and open the table MyTbl, you should get an error of an invalid password. -Now open the form frmConnection and let it stay open, you should now easily open...

Thats true for the normal user, but if you know how it isen't very difficult :eek: just hacked my own test db :p But if your interested here is a securety consept discussed at UtterAccess: http://www.utteraccess.com/forum/Access-2007-security-t1242310.html&hl=midtier JR

There isen't a fullproof way to secure an Access BE, sure you can password protect the BE but the password is exposed in the connection-string to the BE tables so a savy hacker will be able to read it and use it. But for the curious it should stop them from messing with the tables. To fully...

1: <> "Johnson" 2: ="Johnson" JR

Nothing strange about it since your variable test1 is declared as Variant and not as a string. In VBA by omitting a type declaration a variable will be typecast as the default Variant type and variant can handle nulls etc. JR

Can this site help you: http://www.codeforexcelandoutlook.com/outlook-vba/taskitem-object/methods/ JR

See attached. Added a form which uses DCount() to find who gets Discount, note the criteria parameter of the function which points to a form control called MyID that has its controlsource bound to the Customer ID field in the recordsource. JR

It should be: =[listfacility].[Column](1) Nothing more. JR

Could it be that macros like querys do not know what .Column(x) is?? You could perhaps use Eval() function to resolve this. [RecordID]=Eval("[Combo10].[Column](1)") or [RecordID]=Eval("Forms!FormName.Combo10.Column(1)") JR

No problem JR

Put this in the controlsource of your textbox =NameOfListbox.Column(1) Listboxes and comboboxes are zerobased so the "first" column is 0. JR

Sorry about the delay, it was a slight error in the syntax I gave you, should have re-read the link :o Did you look at the link I gave? To refrence a control on a subform you can use the full form refrence or use Me. syntax Full form refrence...

Bookmark this page: http://access.mvps.org/access/forms/frm0031.htm The syntax would be: Forms!SubformControl.Form.Listboxname.Requery JR