Search results

Your code DOES have debug.print lines, but I'm not seeing anything in the immediate window when I run it directly. I'm going to try stepping through it now!!!

Just for confirmation: LoadFromText acTableDataMacro, "tblSource", "C:\Users\<Me>\Desktop\macrosFor_tblSource.xml" from the immediate window works fine, so it is something with the VBA method that isn't working correctly for me.

@jdraw - so it seems to be working for you and not for me. You also had MacrosFor_tblSource.xml in this folder, correct? I have it in a different folder that it was saved to, but it should still work. ??? It does not HAVE to be in the same folder as the database, does it? Tried running it...

Export/Save seems to be working - if that is what you are telling me ... I'm about to leave, but could you look at DM_TestTarget below and see if you see anything incorrect and if it loads for you (which I guess it was earlier.) Thank you again.

In MarshallDM_Test_Target.accdb? Corrected that, Line 230. Shouldn't the DB name be inside the quotes also? I just had the path also ... Basically, I had the strfolder as Optional and I hard-coded it in the FunctionDataMacroFiles. But I tried commenting that line out and passing it the value...

@jdraw - it still doesn't seem to be working for me with your latest #160 changes, but ... Not sure how to interpret this. There were 3 DM's in the source DB TblSource in the source Database. And if it DOES work and copies the DM's, it isn't much help for the future if the DM's are not...

Just tested your #157 code with my #156 database and no difference - it says everything worked, but there aren't any data macros in the DB ...

I forgot to reference the scripting runtime in my DM_Target Db. Also, this is a split DB, but I am opening and editing the test BE directly. Not sure if that matters.

@jdraw - Please look at the attached. I took my database from #69 and re-named it as DM_Test_Source. I made a copy of it and named it DM_Test_Target. I deleted the DM's from DM_Test_Source and imported the VBA from my current test BE. Then I imported the VBA to DM_Test_Target. I opened...

Can you tell me how to use the debug.print statement? Correct. No, this is a copy of the production BE. It's not that I don't trust you, but I'd get in trouble with management if I sent it. Even if I deleted all the records first, it still gives the field names and the processes used. If I...

Thanks - it might not have been clear originally. My test Database has DM's working properly and saved as text. I opened a copy of the original BE that didn't have any DM's and I added the code from #113 to import the saved text DM's to this database. The code SAYS that it ran successfully...

How would I do the printout? I know it is debug.print and it should show up in the immediate window, but where do I put the code?

I'm using the code from #113. I didn't see the SQL in 146 - I think you added it while I was testing. I tried creating a query with it and nothing shows up - which is what I was seeing from the tables in design view. There don't seem to be any DM's, although it says there should be. I'll check...

Still didn't seem to work. I changed everything back and it compiled without errors, and it still says everything was imported, but when I open the table in design view, I still don't see any of the data macros that it was supposed to add ???

That must be what: ' Requires: ' Reference to Microsoft Scripting Runtime meant. I didn't - very little code run from the BE. Testing now!!!

@jdraw - Should have replied earlier, but I'm having problems with the load Data Macros routine from Reply #113. (Didn't test till now - didn't save until now either, but save seems to work fine.): I'm using this: Sub Test() Call DataMacroFiles End Sub I changed StrFolder to Optional and hard...

Figured it out. Below where I commented out: DoCmd.OpenReport "rptErrLog" Add DoCmd.OpenReport "rptErrLog", acViewReport per https://stackoverflow.com/questions/17429709/vba-ms-access-open-report-in-report-view

In this case (and in most cases), I am only adding new tables and or new fields to existing tables, but point 100% taken. From what I've found with the test BE - other than getting an error message when you try to run the query b/c the table field already exists, nothing bad happens. Pat's file...

@ebs17 - You somewhat missed the point of @Pat Hartman's database. The idea isn't to create 50 queries and run them and hope for the best. The idea is to create one query, test in in the test backend. Create another query, test in the test backend. And then run ALL the queries in the...

@Pat Hartman - Challenge accepted. I figured out a little bit what is going on. q001 works fine. q002 gives me an error (as expected and designed). The original version of the database just tried to send a file to my local printer. The modified version pops up a msgbox with "No Current...