How can we help you today? How can we help you today?
Alex D
We have a scheduled task here that syncs error reports into our bug tracker, which is a JIRA 4. I'll email you the source so you can use it as a starting point. Cheers, / comments
We have a scheduled task here that syncs error reports into our bug tracker, which is a JIRA 4. I'll email you the source so you can use it as a starting point. Cheers,
0 votes
I found some advice: The major caveat is that you should only import into an empty database, it is generally not possible to merge two sets of data from different installations of SmartAssembly. The only time you can merge is if they have not used Obfsucation (name mangling) or only used Advanced Unicode, on at least one of the database. Basically the data in the table Names cannot be merged as this would break either the database or the process, so data can only exist in one or neither of the merging databases. Required passwords for single user (Access mdb file) : SA 4 and earlier - cd3409ee69028647 SA5 and later - 7f465a1c156d4d57 Single user (mdb file) 4 to Singler user (mdb file) 5 To overwrite: Open the v4 database (“{database}â€.mdb), change the password and save it over the v5 database (“database.mdbâ€). To merge: Create append queries for each of the tables EXCEPT “Information†Single user (mdb file) to SQL Server instance The important thing to note the schema is not identical between JET and SQL Server, so you should really aim to just migrate the data and not the schema. Run SA5 at least once pointing at the database instance so that the schema is correctly setup. There are various migration tools for Access to SQL Server – there is the Upsizing Wizard in Access or Microsoft have got standalone migrations agents (SQL Server - SQL Server Migration Assistant for Access) for which there are different version depending on which version of SQL Server you are using: MS SQL Server 2008 - http://www.microsoft.com/downloads/deta ... laylang=en MS SQL Server 2005 - http://www.microsoft.com/downloads/deta ... laylang=en You should import the DATA for all tables EXCEPT “Informationâ€. Merging is probably best done by import to temp database and then append queries. Build server (SQL Server instance) 4 to SQL Server instance 5 Nothing to do as long as was SA5 was setup to point to the existing DB. Build server (SQL Server instance) 4 to Singler user (mdb file) 5 Why on earth do you want to do this. Things to note SA5 Pro edition allows you to change which database instance you are pointing at relatively easily. So you could have multiple SmartAssembly databases (only one of which can be a mdb file) imported from different places and just switch between them as required. / comments
I found some advice: The major caveat is that you should only import into an empty database, it is generally not possible to merge two sets of data from different installations of SmartAssembly. Th...
0 votes
Yes, when something complains that two types that look the same aren't the same, it's merging that's broken it. That's a fundamental limitation of any merging technique. / comments
Yes, when something complains that two types that look the same aren't the same, it's merging that's broken it. That's a fundamental limitation of any merging technique.
0 votes