A2007 BE but A2003 FE, how?

spikepl

Eledittingent Beliped
Local time
Today, 09:54
Joined
Nov 3, 2010
Messages
6,142
I have a situation where an A2003 standalone unsplit application needs to read/write data from/to an A2007 backend.

I am not sure that the A2003 can be upgraded to 2007 as is (and cannot test it for the time being) but it does run fine, when executed in an A2007-environment. The entire setup will be operational under A2007.

Assuming that it cannot be upgraded, what are my options, apart from the obvious one, to create some functionality in the A2007 FE and let that link to the A2003?
 
Programs are not forward compatible, I don't think there would is any way you could link or otherwise use an accdb file from a 2003 version of Access, without maybe some type of middlewear that could act as a bridge between the two.
 
Thanks. I am aware of the constraints, so that's why I am looking for a bright idea. I am not sure that data needs to be accessible instantaneously in both places, that is still TBD, so perhaps this could be solved by some import/export.
 
So when I said middle-wear that implied some type of bridge between them, whether that was an import/export of the data from/to flat files, or building a DLL that can interact with both types of database format then using that along with some VBA code to access the data. There are many possibilities, what exactly is the end goal with this FE/BE solution?
 
One is an order-handling system, and the other is a double-entry accounting system, also handling other issues than orders. Somehow I have to end up with all of the order-handling and a lot from the accounting system. The accounting system is pretty complex, and I want to do as little work as possible, so the initial idea is to mess-up as little as possible, but just enough to get relevant data from one to the other. The entire job is constrained by time and money, so the actual outcome is still TBD. I am just sounding out some possible avenues.
 
Well building a custom DLL may fall outside the time/money constraints you're working with then. Given the nature of the changes you want to make it would seem like exporting the data and re-importing it into the other system would be the cheapest/fastest method available to you.
 
I suspected as mch, was just hoping for some miracle. That might still happen, if the 2003 is updateable to 2007, I am just not very keen on testing it, since it is rather involved.

I fear that the fact that the .mdb runs under 2007, is not enough of a proof that a version converted to 2007 would run painlessly, is it?
 
Well I've done several conversions here from 2003 to 2007, and they were mostly painless. There the majority of the Access specific things, like forms, queries, reports, tables, all converted over without any issue. The custom VBA code though had a couple snags, certain arguments left out in the 2003 version became an issue in 2007. The more elaborate the system the more extensive the testing requirements become.
 
Thanks for being a sounding board . I have to do the usual: twice the requirements in half the budget/time, so that's why I am sending out feelers :)
 
Spike I came across this while searching.

Just wanted to say that Late Binding is invaluable in this regard.
 
Thanks RainLover, but there are no references in the DB (other than the default ones). The beast is very tricky (full of little seldom-used features) so I have kept it in 2003, so as not to tickle it unnecessarily.
 
Spike

While you were playing in 2003 did you happen to work out how to hide the Navigation Pane.

I am wanting code that will not error ion 2003 but at the same time work in 2007 and 2010.

I have some users with 2003 and others with 2007. I want the same code for both so as not to have two different Databses.
 
I'll have a look as to what it does when I get there .. it may take a day or two.
 
Thanks

Look forward to your input.

There is a Command in 2007 "NavigateTo" which does the trick by moving to the Nav Pane then hiding it but that command is not available in 2003.

Code:
Function HideNavigationPane(ByRef cCalledFromForm As Form)
If (cCalledFromForm.Modal = True) Then      'If the form is set to modal 
  cCalledFromForm.Modal = False            'Disable modal  
  DoCmd.NavigateTo _
   "acNavigationCategoryObjectType"        'Select Navigation Pane    
  DoCmd.RunCommand acCmdWindowHide    'Hide selected  
  cCalledFromForm.Modal = True            'Enable modal
  
Else                                'Else not modal
  DoCmd.NavigateTo _
   "acNavigationCategoryObjectType"        'Select Navigation Pane    
  DoCmd.RunCommand acCmdWindowHide     'Hide selected  
End If
 
change the backend to A2003. the backend needs to be at the lowest level compatible with the front ends. there is no reason to have it as A2007
 
#14 I had a look (I run it under 2007) , and the Display Navigation Pane is not ticked for the A20003 DB. In the code itself there does not seem to be anything turning the nav pane off.
 
#15. That is a thought thanks for that. I got mentally too stuck on the second FE being 2007 that I forgot that the BE of that one could equally well be 2003.!
 
#14 I had a look (I run it under 2007) , and the Display Navigation Pane is not ticked for the A20003 DB. In the code itself there does not seem to be anything turning the nav pane off.

There is A2207 code to close it but that code causes 03 to fail.

I am getting close to a solution. Will let you know the outcome.
 
what do you mean by navigation pane? do you mean the database window?

in A2003, iniitally it's just just tools, startup, set display database window = false

note that users can then window, unhide, (equivalent to F11 in A2007) unless you take steps to prevent it.
 
I was under the understanding that there is no Database window in 2007 as it is now named "Navigation Pane"

Please correct me if I am wrong.
 

Users who are viewing this thread

Back
Top Bottom