RE: Frontend backend problem
From: don at gypsy (donatgypsy_at_discussions.microsoft.com)
Date: 10/27/04
- Next message: John at Free Design: "Help finding the correct tool"
- Previous message: Albert D. Kallal: "Re: Package and Deployment"
- In reply to: don at gypsy: "Frontend backend problem"
- Next in thread: Brendan Reynolds: "Re: Frontend backend problem"
- Reply: Brendan Reynolds: "Re: Frontend backend problem"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 27 Oct 2004 05:47:04 -0700
Yes, I was trying to go to the table linker. Thank you, that answered one of
my problems. The other problem is that when the db opens an unbound form
comes up. I can input data but when I press the OK button I created to use
this data along with in table info to produce the report it will not work.
Any more suggestions. I am in over my head and can not help but think that I
am missing something very basic. Thanks again
"don at gypsy" wrote:
> I have 2002 access and the developer packager. When I run the frontend db
> application I have created through the packager and then run the packaged
> application on a pc that has access installed, everything works ok, but when
> I install the frontend and backend on a pc that does not have access, the
> frontend can not find the backend -- the forms etc. in the frontend all
> display properly. The backend consists of only tables, which I have
> installed in the properly named folders and files. If I do not split the
> database, the packaged version works find on a pc without Access install.
> I get the following errors (split db) when I try to open the macro that
> opens the table linker or the macro that runs the queries. The expression
> may not result in the name of a macro, the name of a user-defined function,
> or [Event Procedure],
> *There may have been an error evaluating the function, event, or macro
> Another error message I get when I press a button is DEPOSITS can't find the
> wizard, or the wizard has not been installed, or there is a syntax error in
> the Declarations section of a Visual Basic module. Sometimes I get Runtime
> error 75 message
> Thanks for any help
- Next message: John at Free Design: "Help finding the correct tool"
- Previous message: Albert D. Kallal: "Re: Package and Deployment"
- In reply to: don at gypsy: "Frontend backend problem"
- Next in thread: Brendan Reynolds: "Re: Frontend backend problem"
- Reply: Brendan Reynolds: "Re: Frontend backend problem"
- Messages sorted by: [ date ] [ thread ]