Search results

Did you check the "[" at strLinkCriteria? Probably it should be like this: strLinkCriteria="[Cutomer ID]=" & lngCustomerID Only after setting "[" access will accept field-names including space(s).

I've only got half way: Assumption: OLE-objects are in a certain field in a certain table. Then: sub openObjectInWord() Dim oWord As Word.Application Dim dbCurr As Database Dim rs As Recordset Dim oOLE As Object Set dbCurr = currentDB Set rs =...

When using Set db=CurrentDB you definately do not open a DAO-database, but this - current - i.e. JET-database. Did you want do open your own database - which is not connected but this current one - again with DAO? Why? Normally DAO is only worth when accessing other databases (connected)...

Did you copy your database to a local harddisk once? Did this work fine? (I assume: no..) There is some other problem at setting up Access!

Just read the online-help about DIM (private/public). Normally all variables are deleted (and no memory is used) when exiting a sub/function. Just in case you used globals in the header like: Option explicit Dim rsMyRecordset as Recordset Dim dbCurr as Database Sub ... then you should set...

What about the IsFormOpen-function? Probably this doesn't work properly - otherwise it'll put you at least to that MsgBox!

When you open a query by DoCmd.OpenQuery it performs this query just as if you opened it from the database-window. That's why you can format the output of a DoCmd.OpenQuery-command by formatting the output when opening from the database-window. There you select a certain column and set it to...

kindly respect: here it's access-programming

I assume not your export-specifications differ but your tables (diffent field-types, -sizes etc.). In this case this is always enough: DoCmd.TransferSpreadsheet acExport, TableNameOrQueryName, ..otherParameters The TransferSpreadsheet exports no matter how many fields or which fields you need...

don't do: Me.Bookmark = RS.Bookmark If you 'transfer' bookmarks, both recordsets need to be identical! instead use this: set rs1=me.RecordsetClone rs1.FindFirst <criteria> if rs1.NoMatch then goto doSomethingElse me.Bookmark=rs1.Bookmark set rs1=nothing Although: this means you need to find...

Is there any way declaring an OnErrorGoTo-command as default, i.e. this error-routine is used, when any code does not contain an OnError-statement? I have worked a long time with finding a clue to this, cause all variables are emtied if only one error is not handled by an appropriate routine...

Note: All Add-Commands only allow one object to be added (to a certain collection). Why not adding twice like: objMail.Recipients.Add ("person1@domain1.org") objMail.Recipients.Add ("person1@domain2.org") and so on? (hope this works with Outlook)

Just switch to SQL-screen. There you find your query as SQL-string. Copy this to any VBA-module. Then you can (easily?!..) change your query like this: sub test(lngSearchValue as Long) DIM SQL as string SQL="CREATE... " SQL=SQL & "WHERE ThisValue=" & lngSearchValue & ";" DoCmd.RunSQL SQL end sub

1st: be very careful! Normally system tables are hidden, which might be reasonable.. 2nd: all data contained in these tables is made accessible in certain functions. Why not using them? 3rd: which kind of data are you searching for?

Probably Your database is quite corrupted.. I'd try to create a new one and then import all of the old database - until an error occurs. Hope it's only a few ones.. Good luck!

Access the subform via .form: Me.subformName.Form.certainElementInSubform.SetFocus

Sure You need a timed form, as Travis said. This hidden form could check whether You have set a certain field to true (like [Parameters].[close]) and then does Application.Close. Accessing this table in a multi-user-environment is easy, isn't it?

You can just look up whether NewData is already in table: if isnull(DLookup("[CallNo]","CallNoTable","[CallNo]=' & NewData & "'") then ' add new record else ' NewData is in table, do not add end if

Context: MS-WORD accessed by MS-ACCESS Subject: Error -2147023174 (800706ba)at 2nd try One of our Access-databases perfoms VBA-Code in WORD (via object WORD.Application). At the first try, it always succeeds and creates a beautiful document containing all relevant data. But at the 2nd try it...

I agree to jfi: It's not that difficult to hide any Access-parentship by changing the appropriate properties. I suggest: StartOptions: no database-window, start with specific form, disable interrupt-Keys Forms: use BorderStyle=0 (none): now form is just a filled rectangle without title General...