Search results

Bob - thanks for your suggestion. I did try that but it didn't make any difference and I nearly did my back in moving the server closer. I said it was a big server. Dave ps just kidding!! But seiously I don't believe your suggestion is relevant to a default installation of SQL Server on it's...

Access Blaster - sorry if this wasn't clear, but this is, and has always been a split database. From day 1, 5 years ago, it was an Access Front End and an Access Back End for the data. It is the backend that has been "upsized" to SQL Server and the Access Front End was relinked to that instead...

Update:- We were obviously aware of the pitfalls of changing the entire client over one weekend. And we checked with the client but parallel working was not possible due to the nature of their work. But yes we did have a backup plan and yes we have reverted the client to exactly where they were...

Self sorted, thanks

I have a line like this: strSQL = INSERT INTO tbl1 SELECT * FROM tbl2 followed by db.execute strsql, dbFailOnError This works fine but I'd like use a couple of variables for the table names so I can loop through lots of tables. I can't get the syntax right - can someone help please? Thanks...

Just upsized from Access FE/BE to Access FE and SQL Server 2014 BE. Never done this before but all seemed to go smoothly after some weeks of planning. And help from this forum. Went live yesterday. Today about 100 Terminal Services users logged on this morning and all are moaning about...

If I add a table to the BE then obviously I need to re-link the FE. But what about if I add a field to an existing table - do I need to re-link the Access front end to the SQL Server back end? Something I saw recently suggested that I did, but it doesn't make sense to me Any thoughts Dave

Gina - the main reason I want their real data here is that it helps me with support knowing that I am looking at data which is, say, a week or so old at the most. This is really helpful when debugging some of the incredibly complex reports that they ask for.. As you can see from my post I am...

On Sunday I'm converting a large client from Access front and back end to Access FE and SQL server back end. In the Access days I would regularly take a copy of their data file by copying it remotely into Dropbox. I could then run it here in my office and use it for development or bug-fixing...

Self-sorted. First I delete all linked tables on the FE. Then I use a pass through query to enumerate the tables on the SQL server, and then link them all to the FE using a bit of DSNless code from Microsoft.

Thanks for that, but I couldn't find what I need. These programs seem to deal with re-linking whereas what I'm looking for amounts to first time linking. Did I miss something?

I've found and tried code for cataloging all my linked tables and relinking them all to an SQL server, BUT what I need is something simpler, and I can't find how to do it. Starting with a FE with no linked tables, all I want to do is link to every table in an SQL database where the table name...

Using the SSMA and much help from this forum I have successfully upsized a large customer application from an Access 2010 split database to Access 2010 front end and SQLServer 2014 back end. I use ODBC to connect FE to BE and it all seems to work, and user's won't even know it's happened. So...

Thanks to all. In the end I did it the hard way by hunting for every line where I opened a recordset, then adding dbSeeChanges. It took me a whole day but I got there in the end and all is well.

Yes, I see what you're saying. In fact, recently, I have been using much more SQL but of course I still have to open a recordset, so the original problem still exists. Looks like I've a sizeable task on my hands. I will take a look at that link though - thanks for that

Firstly, do you think there might be a way to write a function to go through every line in every module looking for a string beginning "openrecordset" and then perform a fairly early string manipulation to add the required text? Can I use vba on the vba ?? Secondly, not sure why you're...

OK. So I need to add dbSeeChanges everywhere there is an OpenRecordset line. I've tried it and it works fine, but I may have 1000 places to make this change. Can anyone suggest a smart way to do this where:- Most lines are like this: - db.OpenRecordset("tblXYZ") And others are like...

I'm working on upsizing my all Access 2010 front end/back end system to be Access front end and SQL Server 2014 back end. I've immediately encountered the well documented error 3622 having upsized and I have 2 questions I'd like to ask:- 1. Adding the 'dbSeeChanges' parameter is going to be...

Well I think I've cracked it - thanks for persevering with me. This is what I do:- 1. Run the Server Migration Assistant for Access 2. Delete all the table links in my front end 3. Re-link to the SQL server tables using ODBC 4. Rename all the new links to remove the prefix "dbo_" Just for your...

Just tried a pass through query and that worked fine. But I can't see how that helps me. I have about 150 tables in my data and the front end has links to them all where the table name is tblMatters etc. If the table name in SQL Server was also tblMatters then I can link everything via ODBC...