On Thu, May 3, 2012 at 4:20 PM, Ethan Rosenberg wrote:
> At 06:47 PM 5/2/2012, Matijn Woudt wrote:
>>
>> On Wed, May 2, 2012 at 11:43 PM, Ethan Rosenberg
>> wrote: > Dear list - > > Sorry for the attachment. Â Here are code snippets
>> --- Ethan, I don't want to sound rude, but it appears to me y
I don't think posting the same voluminous code is going to generate any
better responses.
The suggestion to start over and make your insert/retrieve queries fool
proof before starting to write some logic into your code was a very good
one. Why don't you work on that so that any requests for he
At 06:47 PM 5/2/2012, Matijn Woudt wrote:
On Wed, May 2, 2012 at 11:43 PM, Ethan Rosenberg
wrote: > Dear list - > >
Sorry for the attachment. Â Here are code
snippets --- Ethan, I don't want to sound rude,
but it appears to me you don't have any
understanding of what you're doing. It might
It is a good habbit to write the core code just for inserting/retrieving
data from database. It will reduce much of your code complexity. When you
see your code is working, you can continue to embed it with your visual
front-end or with your filter.
On Thu, May 3, 2012 at 4:43 AM, Ethan Rosenberg
On Wed, May 2, 2012 at 11:43 PM, Ethan Rosenberg wrote:
> Dear list -
>
> Sorry for the attachment. Here are code snippets ---
Ethan,
I don't want to sound rude, but it appears to me you don't have any
understanding of what you're doing. It might help if you understand
what the code is doing...