Replies

WOW! that was fast – thank you.

Thank you everyone – I found the problem – some idiot (me) had declared the variable SQLSessionDate as date instead of string.

Thank you everyone – I found the problem – some idiot (me) had declared the variable SQLSessionDate as date instead of string.

I have tried surrounding the variable in # eg –
SQLSessionDate = “SELECT tblSession.* FROM tblSession ” & _
“WHERE Session_Date = #” & dteSessionDate & “#;”
with the same result. Running a jet backend but may need to upsize in the future.

I have tried surrounding the variable in # eg –
SQLSessionDate = “SELECT tblSession.* FROM tblSession ” & _
“WHERE Session_Date = #” & dteSessionDate & “#;”
with the same result. Running a jet backend but may need to upsize in the future.

You are right – it did – thanks.

You are right – it did – thanks.

How simple is that! Its times like this I love Access and the Lounge. Thanks Francois

How simple is that! Its times like this I love Access and the Lounge. Thanks Francois

From my experience the most effective approach is to have the stores send their records to the the main server. The basis logic is – the stores have a table with their products and Stock levels. This table has an indicator that is set when the Stock level changes or a product is edited or added. Any changed products are then sent to the server where they update the table on the server. You can do this by periodically running a function that creates a mew mdb and populates it with a table that contains the changed records. This MDB can then be attached to an email that is sent to the server or it can be FTPed. The server has a process that looks for these incoming emails or files which it uses to update its records. These incoming records must identify both the store and the product. It is good if you can coordinate the product IDs so that all stores use the same ID for the same products.
There is a bit of work in this but I have found this the only effective way of achieving your required outcome.

From my experience the most effective approach is to have the stores send their records to the the main server. The basis logic is – the stores have a table with their products and Stock levels. This table has an indicator that is set when the Stock level changes or a product is edited or added. Any changed products are then sent to the server where they update the table on the server. You can do this by periodically running a function that creates a mew mdb and populates it with a table that contains the changed records. This MDB can then be attached to an email that is sent to the server or it can be FTPed. The server has a process that looks for these incoming emails or files which it uses to update its records. These incoming records must identify both the store and the product. It is good if you can coordinate the product IDs so that all stores use the same ID for the same products.
There is a bit of work in this but I have found this the only effective way of achieving your required outcome.

Thanks for the great reply