[AccessD] 2007 autolinking code to backend

I don't have access 2k7 but Check your references.  

Either one of the regular access references is missing or it that
particular function.  You may have moved them to another folder or it
just hiccuped.. I have had that happen when I have done updates.

HTH

**************************************************
* Patricia O'Connor
* Associate Computer Programmer Analyst
* OTDA - BDMA
* (W) mailto:Patricia.O'Connor at otda.state.ny.us
* (w) mailto:aa1160 at nysemail.state.ny.us
**************************************************
 

> 
--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments.  Please notify the sender immediately by reply e-mail and delete the e-mail from your system. 


-----Original Message-----

> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Eget
> Sent: Tuesday, December 11, 2007 07:20 AM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] 2007 autolinking code to backend
> 
> Does anyone have a link to or code to autolink the front end 
> to the backend when a splash screen is opened?
> 
> I cannot figure out the issue below
> 
> I have a database that works fine in 2003, but when I open it 
> in 2007 I get an error code popup when I open my splash 
> screen that states "Invalid procedure call or argument".  I 
> have isolated it (at least I think so) to the following area 
> within the Splash Screen:
> 
> Private Sub Form_Open(Cancel As Integer) On Error GoTo Form_Open_Error
>     ' Check to see if EASILOOK Back End XP is available.
>       If modRefreshTableLinks.CheckLinks() = False Then
>         ' Try to relink the tables; if it fails, shut down 
> EASILOOK Front End XP Application.
>         If modRefreshTableLinks.RelinkTables() = False Then
>             DoCmd.Close acForm, "frmSplash"
>             'Closes EASILOOK Front End XP Application
>             DoCmd.Quit
>         End If
>     End If
>     
>     Call SetEnabledState(True) 'Enables application close and 
> exit capability
>     
>     'Call SetEnabledState(False) 'Disables application close 
> and exit capability
> Form_Open_Exit:
>     Exit Sub
> 
> Form_Open_Error:
>     MsgBox Err.Description
>     CloseCurrentDatabase
>     Resume Form_Open_Exit
> End Sub
> 
> If i comment out the Call SetEnabledState area the form works fine.
> 
> I also have a module that states:
> 
> Public Function SetEnabledState(blnState As Boolean)
>     Call CloseButtonState(blnState)
>     Call ExitMenuState(blnState)
> End Function
> 
> I am at a loss as to why this is happening.
> 
> My Tool-References are as follows:
> Visual Basic for Applications
> Microsoft Access 12.0 Object Library
> Microsoft DAO 3.6 Object Library
> Microsoft ActiveX Data Objects 2.5 Library Microsoft Visual 
> Basics for Applications Extendibility 5.3 OLE Automation
> 
> All of the above works perfectly in 2003
> 
> Anyone have any ideas??
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
>