Search results

Ok Dennisk thanks for the hint, it might come handy along the way I'm sure. Regards, Jaime

Ok, mea culpa, I now understand that I didn't actually wrap the variable in double quotes: ... (WHERE [DateDue] "& op &" Date())... What I really did was seperating the SQL string in 2 SQL strings with the variable in between: "... (WHERE [DateDue]" &op& "Date())..." Am I right...

Thank u Jon K, I'll keep that in mind when building queries in the query builder. As for your suggestion Doc Man, it was clear, it just seems that doing it directly with a variable is easier, in this case. Thanks again guys Regards, Jaime

Ok I followed Doc Man's advice to search the forum and I found the answer in t122314 by Bob Larson. It seems that in order to use a variable in sql you just need to wrap it up in double quotes: Dim op As String op = Me.txtOp 'txtOp is invisible and gets its value (either "<" or ">" ) thru 'a...

Hi there, is it at all possible to use variables in sql? Please consider the following snippet: ... (WHERE [DateDue] < Date())... The idea is to return a recordset where the DateDue is prior to the current date. But sometimes I need the opposite, ie a recordset where DateDue is in the future...

Hi there, What happened with the Access Data Project sample (Northwind.adp) in Access 2007? I searched Microsoft for a download but couldn't find any; can anyone tell where to get one for Access 2007? Thanks, Jaime

Ok let's fix the Year issue first. When you want to use a given year as criterium you must extract that year from a date field. I suspect that in this case tblAllDet.DateRecd is the date field? If so you must do: WHERE Year([DateRecd])=Forms!frmAdvancedSearch!txtYear And ... Good luck, Premy

Thanks again guys, for enlightening this debate Regards, Jaime

Wow, Roy thanks for your reply, this re-launches the debate. Like I said at the beginning there's still seems to be quite some confusion concerning this topic, even among experienced users. I'm glad to see though that Jet isn't altogether unsuited for stuff other than an inventory of one's DVD...

Thank u for your reply, DocMan, I appreciate. Regards, Premy

Thanks guys, for your replies. I think I'd grab this opportunity to warn all beginning Accessers: If you know beforehand that your database will have to be "multiuser on network" at some point, start looking into Access Projects/SQL Server as soon as possible, and don't waste too much time on...

Thanks BrettStah, just seen your reply Well it seems it'll have to be the hard way for me hey!

Thanks for the reply Keith/Wayne. As I suspected, based on other readings, there does not seem to be a real consensus on the subject. Some say it doesn't matter how much you parametrize, Access will still bring down the whole rs, and some say proper parametrizing/filtering will bring down only...

Hi guys, I'm a bit confused: I know that opening a bound form will bring down the whole recordset. But if I create a parametered query as the recordsource, will it still bring down the whole recordset first and only afterwards cut down to the records matching the parameters? Example: I have a...

You mean that the main form is updated when focus moves to the sub form? Do you enter data in the main form before moving to sub? Explain better, pls!

As for books I'd recommend you: Alison Balters Access 2002 Enterprise Developpement, which gives a real comprehensive map road to upsizing and shows most potential problems involved, as well as their solutions/workarounds.

Yep, tehNellie is right. Should teach you to never bite off more than you can chew. Right now I think it'd be better to let yr boss know it'll take longer than u first expected.

What i want to do is to also use this to set the record source for another combo box as well. But Both ComboBoxes are named "Combo12". Could you pls comment the code as to make your intentions somewhat more explicit?

I guess before you started Access, it looked scary too? Just go ahead and learn along the way. Get yourself some books which explain the migration from Access to SQL and learn the rest the hard way: Trial and Error! It's not until you start feeling really challenged by challenges, that DB Design...

Well, I think for issue nr. 1 you should make a query (underlying your form) that takes year as parameter, and then do an If year = Year(Date()) to check if the year (entered in the textbox txtYear on your form) is the current year or not. If it is, set the forms AllowAdditions property to True...