Welcome, Guest. Please login or register.

Login with username, password and session length

Biblesoft Exchange

Pages: [1]   Go Down
  Print  
Author Topic: Authoring System reinstall  (Read 1084 times)
dburgett
Newbie
*
Posts: 1


View Profile
« on: November 05, 2009, 08:55:24 AM »

Ok, I have upgraded to Windows 7, and had to reinstall PCSB 5.0f... I also tried installing BAStag4 and it says "Run-time error '-2147418113 (8000ffff)':  Could not set the CurLine property.  Unexpected call to method or property access"  I have enabled all Macro's in Word 2007 to no avail.  Any suggestions?
« Last Edit: November 05, 2009, 09:09:29 AM by dburgett » Logged
Ted
Administrator
Support Staff
*****
Posts: 1114


View Profile WWW
« Reply #1 on: November 09, 2009, 05:09:18 PM »

Hi -

We're still learning about Windows 7.  Turn off User Account Control and see if that helps.  For the general idea on how to do that (we don't have instructions specific to Windows 7), see the following article in our Knowledge Base:
http://biblesoft.com/new/support/activekb/questions.php?questionid=470
 
Thanks,

Ted
Logged
jenkinsg
Newbie
*
Posts: 9


View Profile
« Reply #2 on: January 07, 2010, 09:04:54 PM »

I'm having the Same problem. Windows 7/Word 2007. User account control is turned off. I opened the debugger and this is what you get:

Public Sub InstallTagTools()

   ' CAUTION:  Modifying and/or disabling the following code violates the Biblesoft Authoring System End
   ' User License Agreement.
   LicenseResp = False
   With BASLicense
      Load BASLicense
      .TextBox1.SetFocus
      .TextBox1.CurLine = 0   <----FLAGGED BY DEBUGGER
      .CommandButton2.SetFocus
      .Show
   End With
   
   If Not (LicenseResp) Then
      Exit Sub
   End If  ' Not (LicenseResp)
   
   CustomizationContext = NormalTemplate  ' apply all changes to Normal template
   UninstallTagTools
   CopyMacros
   CreateToolbar1
   CreateToolbar2
   BuildMenu
   NormalTemplate.Save
   MsgBox "Install successfully completed.", vbOKOnly
End Sub  ' InstallTagTools

If I knew how the VB debugger works, I'd try remming out the line (license warning notwithstanding, just in the spirit of problem-solving), since it doesn't look like something crucial to functioning (and we'd see if there are more errors). If it's simple to explain (can you save from the debugger?), I'd be happy to give it a try. (I'm familiar w/object-oriented programming, just not VB specifically.)
Logged
Blu4est
Newbie
*
Posts: 2


View Profile
« Reply #3 on: January 31, 2010, 01:47:01 AM »

I am also getting the same error on a reinstall (due to a hard disk crash).  I did the same reinstall about 1.5 years ago (not having great success with the hard disk Wink and that went fine - after install PCBS I installed the authoring system macros into MS-Word.  I had been using the macros without a problem.

I am on Windows XP Pro SP3, which is what I was on for previous install.  The only software I know that has changed is IE, which went from v. 6 to 8.  And, the only other thing I know that has changed is the hard disk Smiley

I hope this information helps isolate the problem. 
Logged
JohnB
Experienced User
**
Posts: 441


View Profile
« Reply #4 on: January 31, 2010, 03:59:44 AM »

That is odd Blu4est.

The only problems I ever had with XP was with the security settings in Word having to remove them then reset them to allow macros to run.

Would not have thought that IE should not affect installing the Authoring macros - it should only between you and MS Word.

What version of Word are you using?

I had to install with Word 2007 and it went OK once I found how to alter the security settings although the display of macros is bad - MS problem not PCSB.

JohnB
Logged

ohn
Blu4est
Newbie
*
Posts: 2


View Profile
« Reply #5 on: February 19, 2010, 09:44:54 AM »

I apologize for the long delay.  I have Office/Windows 2002.  Setting the Macro Security to Medium or Low has no effect.  I will try and call SB support today.  Besides the new vs. of IE already mentioned, the only other change I can think of, since my last hard disk re-build, would possibly be moving from XP Pro SP2 to 3.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to: