>You just figure out what the app is
> supposed to do,
> You dont look at the code at all. You just figure out what the app is
> supposed to do, how it's supposed to function, stuff like that, and
> write your cold in CF (or whatever server langauage you're supposed to
> write it in) to work the same way
>
>
>
> ----- Original Message -----
> From: Chunshen Li (Don)
> To: CF-Community
> Sent: Sunday, March 14, 2004 8:34 PM
> Subject: Any Access programmer or ex- Access programmer?
>
>
> Hello,
>
> I'm tasked to develop a web app based on a complex FORM -based
> Access app, which works but has problems.
>
> The design view points me to record source (one query) behind the form.
>
> Q1, what's the role of this query?
> The FORM embeds lots of business rules, lots of functions and/or
> subforms, what's a good way to get to all these functions/subforms,
> their interaction, and equally important, how
> the FORM is going to be processed (maybe, I'm talking in Web terms :),
>
> all the intricacies? What gives me the clue? How could I find the VB
> code for all?
>
> TIA.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
