Search results

Split is the function you want I believe. But you may have to use vba to separate into columns.

I figured it out, was reading some other posts and it struck me, have to have a primary key defined on the SQL table (and represented in the linked table). (Smacks forehead). Dang user designed Access systems I.T. gets stuck with ;) :o

So far every table gives me that error. But the first table is not read only, so that does not appear to be the issue. I have done this before, just this is a new test system I used migration assistant to break the data to a SQL server. NOTES - Design table (in access 2007), compare ODBC...

What would cause Linked Table manager to relink table fine (except read only for some reason) but if I check the always prompt for new location, then it gives me an "ODBC -- call failed" error. I wanted to specify a different DSN, but won't let me get that far. Access 2007 Sql Server 2008...

OK, weirdness. I figured I would create a pass through query just to get a connection string and setup an auto-relink of the tables. Pass through query setup connection string fails (when you click the build button) with ODBC Fail. Before the builder opens. Close that DB, create a new one, do...

Yes I can open the linked tables directly, I can run the queries directly. Only if I run them via the macro do they fail.

Just a thought, why not just keep the data in one table, and add an import date column (or even multiple columns depending on your needs) to keep it all separated? Typically we setup a single import table (per structure) and use that, than use a query to move the data out with additions (like...

Returns 3151 connection to SQL server xxxxx failed. I looked at other macro actions, but none jumped out at me.

The macro does set warnings (off), openquery 2 update queries, Setwarnings (on) that's it. The macro is called from a form close button event. What do you mean by interrogate the DAO?

You would have to resort to VBA to update your query after asking for the table name.

So using migration assistant, I migrated an (2002 format) data tables to SQL Server 2008. Had to relink the tables using the proper ID. When a macro opens an update query, I get an ODBC error. Yet i can run the query by itself with no problems. All table open just fine. Security on the SQL side...

No, it was a unique query name, tried different versions of the names with the same luck. Then ran into a post using BING that someone was having the same issue. They changed it to use DOCMD.DeleteObject acquery and that worked just fine (DOH slaps forehead). We make it too hard sometimes...

Well if I pass it a name that does NOT exist, it creates the Pass Through query fine, so I would say it is the ADOX object (cat in this case) that I am having an issue with for some reason. it is not deleting the current query (does not see it).

DAO is suppose to be on the way out. Of course they have said that for quite a few years now. So I am trying to do it the current way (ADO). I am not getting the error on the properties set now, just the it does not exist on the delete, and the already exist on the append. I added a...

Trying to create a dynamic passthrough query using ADO. So one of the parameters is the query name. cat is an ADOX catalog cmd is the ADO command cat.ActiveConnection = CurrentProject.Connection on error resume next cat.Views.Delete SPTQueryName on error goto errortrap...

I maybe off base, it's been awhile since I have seen this. So you might want to check this. If any VBA code ran, it could set things like turn warnings off, don't save forms (etc.) that did not get reset, and it affects the whole system. Exit and go back in, but don't run anything, and see if it...

Anyone know of good backup software that will work on XP and Win 7? I find it interesting that MS Win 7 won't restore from XP's .bkf file.

have you tried the split function?

You could check how many items are in your combobox, and then do a for loop and remove them, and fill it up again. But I don't think I would put it on the activate. I would make a public sub of it and call it from the form load, and from somewhere else that updates are taking place. But that is...

Where year(tabledate) = FormYear AND month(tabledate) = FormMonth Basically. Of course the FormMonth and FormYear must be numeric values like 2009 and 03 to match unless you go through other gyrations to match them.