Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1140

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1141

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1167

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1167

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1167

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1167

Strict Standards: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1167

Strict Standards: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in /home3/jgbsorg/public_html/Forum/Sources/ScheduledTasks.php on line 1167
Jewish Genealogy in Bavarian Swabia, disclaimer

Disclaimer

The JGBS.ORG web site has been designed and is maintained by volunteers. It receives no external funding. The records have been transcribed by volunteers, mostly amateurs. As a consequence, there will likely be transcription errors. We make every effort to correct such errors, as we become aware of them. We can, therefore, accept no responsibility for consequences that any erroneously transcribed records may cause. If you find such errors, and you are a member of the collaboration, you can tag the respective record by clicking on the "Annotate" icon (the red exclamation mark). If you are not a member, you are cordially invited to become one; or, simply send us an e-mail with details regarding an incorrect record (including record number) and the reason you have for challenging the validity of the data.