Search results

the change is on this line of your code: DoCmd.OpenReport stDocName, acPreview, , "[HWCallDate] >= #" & [Forms]![DateSelection]![Date1]"#" The last part of that line (ie after the last ,) is the WHERE clause of the openreport command. Rich gave you what your WHERE clause should look like...

No you don't need to change the format of the dates in general, just when you use them in WHERE clauses. ie #DateA# BETWEEN #DateS# AND #DateM#, those three date variables should be reformated as mm/dd/yyyy.

How would I know if I have one of them? or how would I create one of them, the SQL will be fairly simple select's if that makes a difference. thanks

I've got data sources as text files and on SQL server databases and I want to store a copy of the data used during the run of the program in an access db. The text files are easy enough, but the sql, well having a bit of a mental block on this: I'm opening a recordset on a SQL server ok, but I...

Your missing an & before the last # but also: You don't use Date2 at all? and you might need to reformat the date to be US (mm/dd/yyyy) format.

I would prod the IT department for more reasoning behind this. I seriously doubt an Access application would be stressing a normal local area network. It would be annoying the hell out of the users long before that! If these access apps are transfering enough data to be causing network...

so opening it dynamic, wont give a proper recordcount? its a pain, as this is should be a simple test...but unfortunatly a sql server down the line is screwed so I can't just run the code:(

In DAO I use: rs.movelast:rs.movefirst icount=rs.recordcount Do I need the movelast/first when I do it with a dynamic rs in ADO? Oh and how will it respond when the rs is empty, or when invalid? is it 0 in both cases or -1? don't suppose it matters, i can check for <1.

You could use an IF do that. But I'm not sure about the mismatch error, that could be your template. eg IF catID=13 then .Item("OthTxt").Range.Text = OthTxt end if

I have had a similar problem where public variables seem to loose their value between bits of code. I never bothered to track it down, and just passed the variables to each sub/func as needed.

So: dim used in subs and functions to declare the dimensions and type of a var. static used in subs/funcs, same as dim, but the value is remembered and used next time sub/func is called. public used outside subs and functions to declare a var that can be used by subs and functions in other...

Didn't think we should be using Global any more? and just be using public instead.

Yea its possible, and its a case of using a different way to reference your objects. In this example it uses the ("objectname") of referencing, and as its a string you can manipulate this anyhow you want. Dim F As Form Dim sN As String 'Open UDField table Set myDB = CurrentDb Set myRS =...

Isn't it just a case of changing this line: LIST1 = ("Email@SomeCompany.com") to LIST1 = ("Email@SomeCompany.com, email2@another.com, email3@endoftime.net") You might need to use ; and not , to seperate (or maybe some other character) If that doesn't work, then cheat:) and loop through an...

Dim is short for Dimension. From the top of the Access 97 Help: In the early days you would have had to define exactly how much space your variable was going to take up in memory. ie the dimensions of the space used.

duh dingbat! One of the problems was that I had a field name, and a text box with the same name as the field but it was bound to a different field. And by defualt access used the control name not the field name.

I've got a similar problem. I use an autonumber internally and want to continue doing that, but I also want an alternative number with a letter prefix, and I want to store it. I've tried various ways of adding a prefix to the autonumber field, but I can't seem to do it, normally the...

Ok, got a solution. Create the following table: CREATE TABLE LinkedTables (TableName TEXT, ConnectStr TEXT[255]) The use the following two subs: Public Sub devGetLink() 'shoves all the linked tables into the LinkedTables table Dim tdf As DAO.TableDef Dim rs As DAO.Recordset CurrentDb.Execute...

no probs, thanks for your time so far! I think I've got an idea...just to see if I can implement it now!

No, the structure is new:( and there will be data manipulation before its linked. I'm trying to think of other solutions...it would be nice if the planned move to SQL server happend earlier rather than later, then I could ditch the frankly poor design entirely.