Search results

Anybody tested how "bad" this performance degradation is on todays computers?

Based on what you say, I'd say it looks like mail merge could be a reasonable suggestion. If you're not familiar with it, check out Albert Kallals "Super Easy Word Merge." from http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html I think perhaps a thought could be to use some form...

Use late binding in stead. This would mean the following declaration Dim WordObj As Object ' Word.Application and, you'd need remove all the wd<constantname> used around and replace with the number they represent. I e in stead of wdRow use 10, in stead of wdColumn use 9 (everything found...

You can refer to each column in a listbox or combobox through an index starting with 0. So for instance (immediate pane) ? Me!MyList.Column(0) ' first column ? Me!MyList.Column(4) ' fift column The bound column, if bound, can be retrieved for instance using Me!MyList or Me!MyList.Value

I'm not sure there is any a simple "rename table" command for DLL. You'll either have to create the table, then append the old data, or use some SELECT INTO syntax (in the interface, that's probably called a "Make Table query") and then drop the old table. If there's relationship, you'll have to...

The_Doc_Man wrote > Roy, regarding your links to ORACLE solution sites: This is just proof of something else that Banana and I have beat pretty hard. When you have database X and have to change to database Y, relying on "side effects" of ZLS or NULL invites total disaster since there is NO...

doco wrote > Hmmm.... using 2003 and don't see it in the properties list or the intellisense dropdowns. This property is available starting from the 2002 version, see for instance http://office.microsoft.com/en-us/access/HP030830011033.aspx (Binding of reports, list boxes, and combo boxes to...

There are no distinct "better table design" or "this is The Solution". There are opinions and preferences (but of course there are cases of "worse table design" ;) ) Null is implemented relatively consistently through database platforms for the purpose of handling missing information. Most...

True that ordinary text fields don't pad, but 1 - if you like, you can also create fixed width text fields, see for instance http://www.access-programmers.co.uk/forums/showthread.php?t=126837, which does pad ;) 2 - not that I'm 100% sure, but I think that the defined size is what's used when...

doco wrote > Is .recordset a valid listbox property? Yup, starting with the 2002 version. Next question, is probably if you can assign a disconnected recordset created on the fly to it, the answer is yes. (Should you need to know whether such recordset can also be assigned to a continuous...

Banana wrote > Interesting as I'm actually trying to avoid zero-length string, because it's confusing. However, I haven't considered that functions would work better with a ZLS than a Null. However, ZLS is usually for a string, whereas I usually use functions for number data types... A bit hard...

For something returning only one field, I could sometimes use ordinal position Me.unid1.Value = rs.fields(0).value but would prefer field name Me.unid1.Value = rs.fields("UNID").value

Ah, I should probably have seen it - it seems you're working with an ADO recordset replace Dim res As New Recordset with Dim res As DAO.Recordset

The important part about the datatype, is what they are defined as in the table. Is the type mismatch on the OpenRecordset line? If so, try opening without where condition - if that's OK, add one of the fields... to check what triggers the error. Edit: Oh, and do a debug.print st and pick...

My guess is that one or both of your parameters are not text, but numeric (RegNo?). I'd suggest removing the single quotes surrounding that/those parameters. Also, dbSeeChanges is a constant, so there's no need for the [brackets] around it.

Are you saying that you are using code residing in form a's class module from form b? If so, you will probably need to qualify it, for instance through the forms collection (which will require the form to be open) Forms!NameOfForm.DisplayAddress(.... Or better, place the code in a standard...

There's also Conditional Compilation #if 1=2 then 100 lines of code debug this, and there should be no error #end if

This sounds like corruption. I'd try the /decompile option. Check out this step by step approach http://www.granite.ab.ca/access/decompile.htm, though, between step 2 and 3, I'd close the database again, then open it (while holding shift to avoid any code running) to compact in another instance...

You're passing all parameters as string, which is a bit suspicious, since you're passing values from a recordset. If any of these are Null, then you'll get errors - but that would probably be RT 94 - Invalid use of Null (or possibly some Byref thingie). Perhaps you should either pass as variant...

I just found a good reference, check out this code from Allen Browne http://allenbrowne.com/func-DAO.html#StandardProperties, which utilizes his SetPropertyDAO function on the same page.