The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Upgrade from 6.1 to 7.0
Posted: 11 Oct 06 7:42 AM
|
fiogf49gjkf0d Hi All,
Currently I'm working on 6.1 for my client. In future they will migrate to version 7. Can any one have idea about how the migration will done?
Thanks in advance  |
|
|
|
Re: Upgrade from 6.1 to 7.0
Posted: 11 Oct 06 3:52 PM
|
fiogf49gjkf0d Hi Swapnil,
I don't have any answers to that but was about to post a question as to the stability of v7. Maybe, when someone answers your post, they could also add something about how v7 is holding up.
Thanks.
Terry
|
|
|
|
Re: Upgrade from 6.1 to 7.0
Posted: 12 Oct 06 9:01 AM
|
fiogf49gjkf0d Click Here for migration instructions for 6.1 to 7.0. If you do not have access to Sage Support online I can email it to you. |
|
|
| |
| |
| |
|
Re: Upgrade from 6.1 to 7.0
Posted: 28 Dec 06 4:52 PM
|
fiogf49gjkf0d RJ,
Glad someone has already done the 5.2 to 7.0 upgrade. I saw the responses to my Newsgroups questions about the index removal stuff, but I'd like to pose another question. In the past (5.x to 6.x, etc.), I was able to upgrade an Slx database separately from the base software. That is, do a forced restore of a 5.2 database onto SQL server in the 6.x environment, apply the upgrade utility, and then install the new bundles in the new environment. But this time, the Upgrade Manual is telling me to do it (upgrade and install the 7.0 bundles) in the old 5.2 environment. Is it possible to move the old database to the new environment and then apply the upgrades routines and install the new bundles?
Bob Levine
|
|
|
| |
|
Re: Upgrade from 6.1 to 7.0
Posted: 29 Dec 06 8:40 AM
|
fiogf49gjkf0d Mike,
Thanks, and yes, I just went back to the Upgrade Manual and it clearly states that the bundles are applied via the V7 Administrator. I not sure where I picked up the idea that it was via V5, but I'm glad I was wrong.
And to all, have a HAPPY NEW YEAR ! |
|
|
|
Re: Upgrade from 6.1 to 7.0
Posted: 31 Jan 08 3:37 AM
|
Originally posted by Bob (RJ)Ledger
Oh yes.. you need to completely re-implement the customs for:
Account Detail
Contact Detail
Opportunity Detail
Product related stuff..
--
rjl |
|
We are looking at upgrading from 6.1 to 7 and I have read this post with interest, could you be a bit more specific about the term re-implement? Is that as in completely rewrite, or is it a matter of having to re-release and possibly setup again in user profile security?... Thanks in advance. |
|
|
|
Re: Upgrade from 6.1 to 7.0
Posted: 31 Jan 08 5:21 PM
|
The problem that you have is that the OOTB SLX forms have been modified in V7.
Your ideal way forward is to start with the most recent OOTB versions and reapply (and re-test) your customisations - so you take advantage of all of V7 improvements while maintaining your customisations.
Hence the term 're-implement'. It should not be a rewrite at all - most of your customisations will work in V7 exactly as they do in 6.1.
Phil |
|
|
|
Re: Upgrade from 6.1 to 7.0
Posted: 01 Feb 08 3:44 AM
|
Thanks for the clarification.
Something that has thrown us in v7 is the fact that the setting in the User’s Security Profile now works as documented, i.e. "If the views you set for Detail View and Lookup View become unavailable for any reason, the settings change to "Use default view" and the user will see the default views. (For example, if you modify a form in Architect and re-release the plugin, the old version of the view is no longer available. The user will see the default view until you select the new version of the view in the user's profile.)". I believe this was broken in 6.1, but had the benefit of allowing us to amend the Detail Views without having to worry about resetting all of user profiles! We have 4 different Detail Views assigned to a mix of 120 users, so having to change these settings could pose a nightmare - ah well, one for the admin |
|
|
|
Re: Upgrade from 6.1 to 7.0
Posted: 01 Feb 08 4:49 PM
|
EASY fix for the 4 different "views" - It's called "Panels"...
Use ONE form.. and put each "view" on a panel. Alter teh panel visible property on AXFormChange based on the "team" the CurrentUser is part of...
Here's a function that you can use to test the Application.BasicFunctions.CurrentUserID:
'
'Determine if a user is a member of a given Team or Department
'
'
'Example of use:
' If IsMember("UFFED0000027", "Development", "D") = True Then
' MsgBox "Is a member"
' Else
' MsgBox "Is NOT a member"
' End If
'Or
' If IsMember("UFFED0000027", "Midwest", "T") = True Then
' MsgBox "Is a member"
' Else
' MsgBox "Is NOT a member"
' End If
'
' sGroupType = "T" for team, and "D" for department
Function IsMember(ByVal sUser, ByVal sGroup, ByVal sGroupType)
Dim sSQL01
Dim objRS
Application.Debug.WriteLine "IsMember >>"
On Error resume Next
If sGroupType = "T" Then
sGroupType = "G"
End If
'Application.Debug.WriteLine "DEBUG - " & sUser & "," & sGroup & "," & sGroupType
Set objRS = CreateObject("ADODB.Recordset")
With objRS
Set .ActiveConnection = Application.GetNewConnection
sSQL01 = "SELECT ACCESSID FROM SECRIGHTS WHERE SECCODEID = " & _
"(SELECT SECCODEID " & _
"FROM SECCODE " & _
"WHERE (SECCODEDESC = '" & sGroup & "') AND" & _
"(SECCODETYPE = '" & sGroupType & "')) AND " & _
"(ACCESSID = '" & sUser & "')"
.Open sSQL01
If Not (.EOF or .BOF) Then
IsMember = True
Else
IsMember = False
End If
.Close
End With
Set objRS = Nothing
Application.Debug.WriteLine "IsMember >>"
End Function
|
|
--
RJLedger - rjlSystems |
|
|
| |
|
Re: Upgrade from 6.1 to 7.0
Posted: 09 Feb 08 7:17 AM
|
Yep... I use this function in 99% of the implementations we do..
--
RJLedger - rjlSystems |
|
|
|