Recent content by AlanJ10

So I see. I've already had problems with office 2003 and 2007 installed at the same time, but I was hoping that Access Runtime wouldn't cause the same issues. It's pretty much out of my hands then, either my client will need to have a 2003 machine so they can create 2003 mde files, or they'll...

I'm trying to put together a database that is capable of exporting mde files. The database is currently in 2000/03 format, but will most likely be run on 2007 machines, which will produce 2007 mde (or accde) files. The people that need to run the mde files, will most likely have Office 2003...

Access 2003 and that option fixed it for me. Cheers Bob.

I'm trying to remove user-level security from a database I wrote a while ago. I've created a fresh database and exported everything from the old one, but some of the forms look different. All the fields that were sunken are now flat, and all the tabs have a solid white background instead of...

Thanks for that. Is there anyway I can set the connect property to have a path that doesn't exist (I haven't actually tried this for a bit, but I think refreshlinks either doesn't do anything, or gives an error, I don't remember). It looks like the best way is to just put something in so that...

Is there anyway I can create a linked table to a database that "doesn't exist" (ie. is on a network that I don't currently have access to, but the users will have access to)? At the moment, I'm working around it by having the database check the links on startup, so when the user opens it up they...

Right, I'm back. I'm now trying this in 2007, but have discovered that MDEs seem to have disappeared to be replaced with ACCDE files. I've tried my code in 2007, but it fails silently when creating the MDE/ACCDE file. Is there a different method to creating an ACCDE in vba in 2007? Edit -...

Just a straightforward strFilename = "Path to database here", so it made no sense at all. I seem to have got it all working now by putting the makeMDE code into a separate function and calling it as part of my code. Thanks for your help.

Right, I seem to have resolved my above problem using convertAccessProject, but I'm still getting "Run-time error '7952' You made an illegal function call" when I try to create my MDE file (using appAccess.SysCmd 603, strFilename, strFilenameMDE). Any ideas? Edit: Not entirely sure what I've...

I know this, I want to do the whole thing as a process in vba: 1. Create new mdb 2. If necessary, convert to 2003-03 format 3. Convert to mde I can do 1 and 3 ok, but I don't know how to do 2.

Ok, that's fair enough. So, how can I create a 2003 MDE given my situation above. Easy answer is presumably to set my default file format to 2003, but I can't guarantee that the people running this will have the same setting (in fact, I can't guarantee what version of access they'll be running...

That's something I'd better check actually, but just to be clear, I can only create a 2003 MDE from my installation of Office 2003? What software will someone need to run this 2003 MDE? Sorry, I've never actually done anything with MDE files before, so trying to create one like this is sort of...

Ok, I've tried to summarise my dilemma in the title, but I've thought of a few ways I might achieve it, I'm just not sure how to go about any of them, or which might be the correct one. I'm running Access 2003, which is set to create 2000 format databases by default. What I want to do, is...

That looks pretty handy, thanks a lot.

Sorry, I'm explaining myself really badly. I don't want to set DoCmd.SetWarnings True because I don't want the enduser to see it/have to click ok, I was just wondering if there was anyway to capture the number of records affected by the SQL and then use that in my code, ie. docmd.setwarnings...