Replies

Thanks that is more or less what I ended up doing also. Just wondering if there was anything else.

here is some code from Dev Avish, that I modified to use a registry setting. I always appreciate his code and am very grateful

This is not the place to discuss Office 2010 Beta. Moreover, this topic is about starting Excel from Access, please don’t hijack it.

Sorry you are correct

Is Office 2010 on its’ way?

I ave been using the technical preview (beta). Not any major changes in the front end of Access, did not yet get a chance to sue the new macro editor which look interesting. Also they redid the build button in creating Dfunctions etc. However, Outlook 2010 is great.

The code itself is correct, so there appears to be a problem with the Excel object. Does the problem persist after restarting your PC?

due to some other issues also I uninstalled 2010 and 2007 then reinstalled only 2007, but I still have the issue. Very weird and annoying.Still have not had a chance to try it somewhere else

The code itself is correct, so there appears to be a problem with the Excel object. Does the problem persist after restarting your PC?

yes. I think it might be because I have both 2007 and the beta of 2010 installed on my computer. I am going to try this on a simpler instal and see what happens.
Thanks

Is there other code between the line

Set appExcel = CreateObject(“Excel.Application”)

and

Set wkb = appExcel.Workbooks.Add()

that you haven’t posted?

no- just the rest of strsql that is just a string that I checked already works.

Does it make a difference if you omit the brackets?

Set wkb = appExcel.Workbooks.Add

No, I had tried that first.
Thanks

Open the database on a PC with Office 2003.
Delete the reference to the Microsoft Word 12.0 Object Library, then set a reference to the Microsoft 11.0 Object Library.
Check for other missing references too.
The database will then work correctly for both Office 2003 users and for Office 2007 users.

Just a reminder that the next time he does developement work on his computer with 2007 the references will go back to Office 12 and before you pass it on you need to reset these references again.

Brilliant. A lot easier than reacordset clone.
Thanks as usual

You can use the built in database documentor in database utilities

It still jumps back to the first record on the subfom.Istere any way to stay or retrn to the record I was editing

Try

Me.Parent.Recalc

Another option that is much more expensive is FMS Total Access Analyze ,but it does what you need and a lot more. I have used it http://www.fmsinc.com/MicrosoftAccess/BestPractices.html%5B/url%5D

In other words there is no docmd…. that calls the mail merge wizard?

I am going to try it in stages, but first I need to get my main computer repaired so it will take a some time. Thanks for the encouragement.
If I am using accdb and there is no replication support, then I am really unable to have concurrent usage? Is that correct?