Project data changing after loading project into different software versions

Shane Regan — Mon, 24 Aug 2020 09:13:46 GMT

Current Revision posted to Hevacomp Wiki by Shane Regan on 8/24/2020 9:13:46 AM

	Product(s):	Hevacomp Mechanical Designer
	Version(s):	V8i (N/A)
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem

Loading a project created in the latest software version into an earlier software version can lose data. Loading back into the current version does not resolve this.

Solution

Project data is stored in a number of files and database locations within a project. For earlier versions of the software, these files and locations may not even exist. Bentley Hevacomp always allows you to bring a project into a new version of the software, but strongly advises against taking a project into an older version of the software.

Ideally, you should ensure that all users are running the latest, most up to date version of the software. Viewing the RSS feed within the latest software versions, or subscribing to this Wiki will ensure you are informed about updates and changes.

Project data changing after loading project into different software versions

Duncan Brown — Wed, 07 Jun 2017 10:30:27 GMT

Revision 2 posted to Hevacomp Wiki by Duncan Brown on 6/7/2017 10:30:27 AM

	Product(s):	Hevacomp Mechanical Designer
	Version(s):	V8i (N/A)
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem

Loading a project created in the latest software version into an earlier software version can lose data. Loading back into the current version does not resolve this.

Solution

Project data changing after loading project into different software versions

Duncan Brown — Wed, 07 Jun 2017 10:29:54 GMT

Revision 1 posted to Hevacomp Wiki by Duncan Brown on 6/7/2017 10:29:54 AM

	Product(s):	Hevacomp Mechanical Designer
	Version(s):	V8i (N/A)
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem

Loading a project created in the latest software version into an earlier software version can lose data. Loading back into the current version does not resolve this.