Versions 8 and 9 on same computer

[CALocklin]

Re: Versions 8 and 9 on same computer

I am wondering about this also. But my specific situation is reversed. I want to open tables currently being used in A5v9 with my A5v8 software.

Will Don have a problem now with his client using version 8 if he makes changes in version 9?

Will there be any problems either way if we only open tables in either version and make changes but do not change the application files?

Thank you
Sean

Don's problem is entirely different. It only arises because he's using the .adb file to create the shortcut instead of the .exe file. He has V8 on his computer as does the museum so versions aren't really a concern.

Only Alpha tech or the other gurus in this forum can tell you all the nuances of the two different versions. All I know is that I went from V4.5 to V8 seamlessly. From reading the threads in the two forums, differences may arise if you do programming but I don't think that just editing (i.e., making changes) in a table would be any different to either program. I'm sure someone else will chime in here (see David Boomer's post near the top of this thread).

Once you design/edit something in a higher version, there is no guarantee that it will work in an earlier version. If you're lucky, it might but don't count on it. If you do it, you better have a backup of the application in the old version just in case.

The general rule is: If your users are working in one version, DON'T design/edit anything in a higher version and expect it to work.

The biggest issue will be with layouts. Global scripts and functions (those listed in the Code tab) probably won't matter.

Also note that I'm talking VERSIONS here as in v8, v9. In the vast majority of cases, using a later build of the same version won't cause a problem - but, again, no absolute promises. Basically, if you use a new feature that was added in a later build, it obviously won't work in an earlier build. If you don't use a new feature, it's generally not a problem to go back and forth. However, sometimes it's rather wierd what can "break" even between builds. I generally don't worry about changes in builds but I keep the idea that this might cause a problem in the back of my mind just in case.

On the flip side, most things can easily be moved from an earlier version to a newer version with little or no "fixes" required. You might want to update to some new features but that's a different issue.

[dik_coleman]

Re: Versions 8 and 9 on same computer

This is for Mike C -----

I always make my shortcuts from the 'Tools' Menu when I know I am in a
specific build/version of Alpha 5. At this point, I have never had a problem
with such a shortcut 'migrating' to a later build/version of Alpha 5.

First, I try to put new versions of A5 on different drives so that I can more
easily differentiate between them. Even if they were on the same drive, they
would be in different folder hierarchies.

Are you saying that installing a newer version of A5 could/would/might/will
automatically cause older versions to 'migrate' to the new version?????
And how widespread would this be??????

Confused
D

[MikeC]

Re: Versions 8 and 9 on same computer

Richard,
My comments are in regard to the development shortcut that is placed on the desktop when Alpha is initially installed on a computer. I have had the old issue of when installing a runtime on the same computer that the original Alpha icon that was for development had its shortcut changed to the runtime. I have also had QReportBuilder v9 replace my QReportBuilder v8 shortcut...on one machine....transferred both these versions to a different computer and it was fine---so not an "always" situation as I pointed out, but just something to watch out for (and really not a hard thing to fix either...and not something that would keep happening either).